For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Chris_Guthrie's avatar
Chris_Guthrie
Icon for Nimbostratus rankNimbostratus
Mar 27, 2017

Azure SAML IdP

So we have an external IdP that is created using the federation information that we can download from our Azure account.   https://login.microsoftonline.com/{customer_id_string}/federationmetadata...
BIG-IP
BIG-IP Access Policy Manager (APM)
devops
Sergi_Munyoz_24's avatar
Sergi_Munyoz_24
Icon for Nimbostratus rankNimbostratus
Mar 27, 2017

Which version are you using ? I'm at 12.1.1 204 I think The other day I was setting up federation with IBM verse and I did find F5 imported incorrectly certs from metadata, maybe is a bug we can report. IBM has two, one for signing, one for encryption. Common names were like IBM_VERSE_S and IBM_VERSE_E. But when I came to the gui, to my surprise both were as IBM_VERSE_E What I did was, edit metadata with notepad, copy text for both certs between < and > and paste with notepad in a .txt and rename to .cer Then I imported back to gui and reassigned them to SP-connector Then certs show correct name and everything begin to work