on 11-14-2013 9:31 AM
Hello Experts
We have configured SSO between non sap portal & sap portal 7.3 with SAML 2.0. Our SAP portal is acting as service provider. We have maintained the relay state paramter as shown in below for irj/portal
Our SSO is working fine for irj/portal
We also have sourcing 9.0 deployed on top of our portal system whose URL will be like https://<dns>/demosourcing/fsbuyer/portal/login. In this case the context is getting changed. How we can maintain multiple application path for same relay state parameter?
Thanks
Atul
Hi,
Application Path and RelayState Alias
RelayState : private
Application Path:
/example/private |
Note:
The service provider supports adding URL parameters to the relay state alias. The service provider strips the URL parameters from the relay state alias and appends it to the matching application path, even if the application path already includes URL parameters. Using the example above, the service provider receives a relay state, private?test=true. The service provider redirects the client to /example/private?test=true.
BR,
Prabhakar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Relay State | Application context | Remark |
https://abc.com | /irj/portal | Currently maintained |
https://abc.com | /abcsourcing/fsbuyer/portal/login | Need to maintain. Not allowing to maintain for same relay state. |
Looking for how to maintain multiple application context for same relay state.
Thanks
Atul
Pls checck ...http://scn.sap.com/message/13970601
Hi Prabhakar,
SAP OSS team, came back with the following suggestion. Need help in developing a portal application and make portal application as below.
Thank you for the clarification. I inspected the attachment and I
confirm again that this mapping is not possible. You cannot have one
relay state mapped to more than one application path. And an additional
remark - it is not good that you give URL-s for the relay state, just
pick a plain descriptive string like 'portal' or 'abcsoursing' for
instance.
The idea of using the URL parameters is that on the SP side you create
an application with path, for instance '/redirect/app'
Then you define a relay state, say 'redirect_app' with value the above
application path. Then on the IdP side you have to configure the
links to be for that relay state and with specific URL parameters, for
instance:
http://<sp.host>:<sp.port>/redirect_app?target=app1
http://<sp.host>:<sp.port>/redirect_app?target=app2
http://<sp.host>:<sp.port>/redirect_app?target=app3
When received at the SP side they will be converted by the SP to these
URL-s:
http://<sp.host>:<sp.port>/redirect/app?target=app1
http://<sp.host>:<sp.port>/redirect/app?target=app2
http://<sp.host>:<sp.port>/redirect/app?target=app3
and the browser will be redirected to the redirect application with the
current target URL parameter. Then the redirect application will just
redirect to the application denoted in the target parameter, say:
http://<sp.host>:<sp.port>/app1
Regards
Ponnusamy
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.