![]() ![]() If the attribute statement from IDP that has the userID value is userAttr.urn id:XXX.XXX. So in example 2, the signed in user was urn: oid:Ó and example 5 returned uidÓ If I leave out the brackets, the value that gets returned as the UserID is literally what is typed in the Name Template Field. I tried various other methods like:ġ) (where XXX is the object identifier for our userID attribute)Ħ) When I use the examples that begin with Ó, I get Invalid Assertion ErrorÓ on the juniper side after authenticating. That allows me to login, but the UserID from the juniper logs is some random string of numbers which means nothing to us because we canÕt correlate that back to an actual user. I first tried to leave the field blank so that it gets the name identifier from the entire assertion. , attr from AttributeStatement attributes. The Junos Pulse Secure Access Gateway Series device identifies user sessions that connect with the Junos Pulse clients by the local machine identifier, which is sent to the server, when a connection is established via Junos Pulse. The entire assertion name identifier if not specified Or On the juniper appliance under the Auth ServerÓ configuration page, there is a User Name TemplateÓ field where youÕre supposed to define the attribute name for the userID. ![]() ![]() IÕm having issues getting the Juniper appliance to pick up the userID from the attribute assertion. Can you help determine what the proper syntax is for the user name tempate field when our SAML attribute statements are passed through as Object Identifier Numbers? ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |