 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / ASP.NET / Web Services / March 2006Custom SecurityTokenManager: User.Identity
When implementing a custom SecurityTokenmanager, when is it appriopriate, and how, should the user.identity be set in the context? Shouldn't the user be available in the User.Identity-class if the token is a per-user token? Hi, You should implement a custom SecurityTokenManager when you want to customize something in one of the existing token managers (Username, X509, Kerberos, etc) or when you want to use a custom token and WSE does not provide a token manager for it. For example, if you want to customize the authentication process for username tokens (To authenticate the user against a database), then you should modify the UsernameTokenManager. Another example, you want to use a SAML token. In that case, you will need to implement a custom SecurityTokenManager since WSE does not provide a token manager for SAML. The user should be available in the identity token -> RequestSoapContext.Current.IdentityToken Does it anwer your question ?. Regards, Pablo Cibraro http://weblogs.asp.net/cibrax > When implementing a custom SecurityTokenmanager, when is it appriopriate, > and > how, should the user.identity be set in the context? > Shouldn't the user be available in the User.Identity-class if the token is > a > per-user token? Thank you for the reply. I've been working with the SAML STS for WSE3 (MS Quickstart), which includes a TokenManager for SAML tokens. Even though the authentication is successful, RequestSoapContext.Current.IdentityToken is empty, so I'm guessing there must be something wrong with the token manager. Where should I set this identitytoken? The RequestSoapContext.Current is null in the token manager. > Hi, > [quoted text clipped - 25 lines] > > a > > per-user token? RequestSoapContext.Current.IdentityToken isn't null, but its Identity and Principal properties are empty. > Thank you for the reply. > I've been working with the SAML STS for WSE3 (MS Quickstart), which includes [quoted text clipped - 32 lines] > > > a > > > per-user token? Yes, you are right. That is a bug in the quickstart. I have already reported the solution in the message board of the GDN workspace. http://www.gotdotnet.com/codegallery/messageboard/thread.aspx?id=8da852b9-2c0d-4 eb7-a2de-77222a4075f6&mbid=266a93e5-df21-4275-afa5-c7c9f109a8a1&threadid=88e858d f-f9d0-4f20-9000-6d8a63418344 Thanks Pablo. > RequestSoapContext.Current.IdentityToken isn't null, but its Identity and > Principal properties are empty. [quoted text clipped - 43 lines] >> > > a >> > > per-user token? Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.