on 09-19-2008 11:10 AM
Hi Folks,
I will be writing a desktop based application in Adobe Flex/Microsoft .NET which would be based on web services. I have a coupl eof questions.
1. I wish to know how to authenticate the user i.e. say I create a login sreen in my application and accept the user's sap netweaver user/pwd, now I wish to know if there is already any standard web service that can be user to authenticate? If there is no standard web service then how can I achieve this?
2. The next question is even if I am able to do the first step and authnticate the user, how do I maintain the session i.e. the subsequent web service calls should not ask for user credentials.
Thanks & regards,
Gaurav
You may use WS-Security SAML Token Profile, to achieve Single-Sign-On between SAP netweaver and .NET.
1.The user logs on to the Windows domain with his Windows Credentials.
2.The WS Consumer authenticates at the Token Issuer with Windows Integrated Authentication and requests a SAML HoK Token that contains the domain identity.
3.The Token Issuer issues the SAML Token.
4.The WS Consumer sends the request using the Custom Binding (WS-Sec 1.0, SOAP 1.1, SAML Token Profile 1.0).
5.The WS Provider maps the Windows User identity to the ABAP User identity.
6.WS Provider sends response.
p/s: supported in SAP NetWeaver 7.0 >= SP14 (ABAP)/SAP NetWeaver 7.1 (Java, ABAP).
- julius
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My last post was on Message level.
Perhaps another simpler approach at transport level is to use SAP logon ticket for SSO.
See this sample:
- julius
Thanks folks! I'll wrok on all the ideas that you've put forth and see if it works out for me.
Regards, Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You could use HTTP authentification for instance. The user would have to provide valid credentials for each WS call. Instead of "maintaining the session" you could ask the user for his/her username/password, then store the data somewhere and pass them each time the app calls a WS.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
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.