I’m about to implement a SP-initiated SAML connection to our BigIP APM, set up as IdP, currently v15.1.2, eagerly awaiting some bug resolutions for the upgrade to 16.1.
I want to suppress the “login name” prompt on the f5 and just to ask for the password by extracting the login name from the NameID value.
IMHO, there’s no need for the enduser to enter his name twice, first at the SP’s and a second time at the APM login window.
Any clues?
Many thanks and best regards from Basel, Switzerland,
sorry for the lame question,but if F5 is acting as IDP, shouldn’t it have access to nameID already? It will generate the SAML assertion after authentication with domain controller. on F5, we would have to set AD query to retrive attributes from AD and set nameID accordingly (e.g. email/UPN etc).
Yes and no, SanjayP - you are way further in the process than my question…
YES: It should know the NameID, but
NO: Not from the AD/LDAP-Lookup, but from the SAML Authnrequest.
Elaboration: My process is:
User clicks on SP’s login page on “authenticate with SAML” and is prompted to enter e.g. his email address
SP decides to send an Authrequest to our f5, as this is our IdP. THIS CONTAINS THE NAMEID AND THE SUBCECT ATTRIBUTES. Both contain the user’s email address
WHAT I WANT TO DO NOW on the f5: Extract either of those Attributes, treat them (ie. cut the @domain part) and set session.last.username.
Show a login window with just a password prompt (as we already know the user name).
NOW do the LDAP authentication, LDAP lookup, and calculating the SAML Attributes for the SP. (Thats’s where you think we are already - if I get your post correctly).
Issue the SAML assertion for the User for connecting the SP.
SP does - based on the provided SAML attributes - the authorization for his services and grants access accordingly.
but it appears authrequest doesn’t have any attribute set if it’s SP initiated SSO. Are you sure, you can see email address in authrequest?
ACCESS::saml authn [value] will not work, as that is triggered only when F5 generates the payload.
This would need to check first, how emailaddress is being sent (either any part of header, uri or payload) and write iRule to extract that, set custom session parameter with that and use in login page.
OR present F5 login page, with username/password field and take it from there. (which you are already doing it), but I understand it’s not user friendly.
> This would need to check first, how emailaddress is being sent (either any part of header, uri or payload) and write iRule to extract that, set custom session parameter with that and use in login page.
But what I still am confused about: Am I really the first person on earth trying to omit that users have to enter redundant logon name twice? Simply can’t imagine that this wheel isn’t invented yet.
Since SP and IDP sessions are totally diffrent and independent of each other, it would need custom rules built to extract the user. Not seen that’s been implemented many places. We will keep the forum open for other to provide any inputs if there is any easy way to extract this.
On seperate note, how about modifying the page at the SP end to omit the field for user and just have sign in button, which will redirect the user to IDP and user would have to put it only once on IDP page? I know this isn’t ideal option but just thinking out loud.
It is handled the same way as the Microsoft Auth Page, you need to first specify a NameID (first.last@domain.com) and then the Authenticator recognizes the @domain.com and is redirecting then to the IdP.
It seems that the only way to get the entered username in a SAML SP Initiated session is to read the referrer header and get the username parameter out of it.