218
Novell Access Manager 3.1 SP2 Identity Server Guide
n
ov
do
cx (e
n)
16
Ap
ril 20
10
<identity consumer URL>
?PID=
<entityID>
&TARGET=
<final_destination_URL>
The
<identity_consumer_URL>
is the location of where the authentication request can be
processed. For an Access Manager Identity Server, the URL is the Base URL of the server that is
providing authentication, followed by the path to the protocol application being used for federation.
For example:
SAML 1.1:
https://idp.sitea.novell.com:8443/nidp/saml/idpsend
SAML 2.0:
https://idp.sitea.novell.com:8443/nidp/saml2/idpsend
Liberty:
https://idp.sitea.novell.com:8443/nidp/idff/idpsend
If a third-party server is providing the authentication, search its documentation for the format of this
URL.
The
<entityID>
is the URL to the location of the metadata of the service provider. The scheme (http
or https) in the
<entityID>
must match what is configured for the
<identity_consumer_URL>.
For
SAML 1.1 and SAML 2.0, search the metadata for its entityID value. For Liberty, search the
metadata for its providerID value. Novell Identity Servers acting as service providers have the
following types of values:
SAML 1.1:
https://idp.siteb.novell.com:8443/nidp/saml/metadata
SAML 2.0:
https://idp.siteb.novell.com:8443/nidp/saml2/metadata
Liberty:
https://idp.siteb.novell.com:8443/nidp/idff/metadata
If you are setting up federations with a third-party service provider, search its documentation for the
URL or location of its metadata.
The
<final_destination_URL>
is the URL to which the browser is redirected following a successful
authentication at the identity provider. If this target URL contains parameters (for example,
TARGET=https://login.provo.novell.com:8443/nidp/app?function_id=22166&
amp;Resp_Id=55321 &Resp_App_Id=810&security_id=0
), it must be URL encoded
to prevent the URL from being truncated.
Examples with all three parts:
SAML 1.1:
https://idp.sitea.novell.com:8443/nidp/saml/idpsend?PID=https://
idp.siteb.novell.com:8443/nidp/saml/metadata&TARGET=https://
eng.provo.novell.com/saml1/myapp
SAML 2.0:
https://idp.sitea.novell.com:8443/nidp/saml2/idpsend?PID=https:/
/idp.siteb.novell.com:8443/nidp/saml2/metadata&TARGET=https://
eng.provo.novell.com/saml2/myapp
Liberty:
https://idp.sitea.novell.com:8443/nidp/idff/idpsend?PID=https://
idp.siteb.novell.com:8443/nidp/idff/metadata&TARGET=https://
eng.provo.novell.com/liberty/myapp
If you are configuring an Intersite Transfer Service URL for an Identity Server that is the identity
provider and the service provider is either another Identity Server or a third-party server, you can
simplify the Intersite Transfer Service URL to the following format:
<identity consumer URL>
?id=
<user_definedID>
Summary of Contents for ACCESS MANAGER 3.1 SP2 - README 2010
Page 4: ...4 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 12: ...12 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 158: ...158 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 172: ...172 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 182: ...182 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 290: ...290 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 362: ...362 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 374: ...374 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...