Hi All,
I have configured the SAML SSO authentication with relevant IDP details (Admin --> System --> Authentication).
Now, I need to configure my IDP with details of RSA IMG as the service provider for details like saml assertion consumer endpoints etc.
I believe service providers usually publish this information as an accessible URL or through a file export.
How can I get this SP metadata for RSA IMG Aveksa please?
The version I am using is 6.0
Regards
Ajay Suri
Hey Ajay Suri,
Have exactly the same question, did you somehow manage to acquire the SP metadata?
Regards,
Jay
RSA VIA does not provide a Service Provider (SP) metadata. But you can use something (SAML 2.0) like this for configuring on your federation product.
You will have to update instance specific configurations like the X.509 certificate for your VIA instance (YOUR-VIA-X.509), the VIA assertion consumer endpoint https://rsa-via-hostname.com/aveksa/main
<?xml version="1.0" encoding="UTF-8"?> <md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" validUntil="2016-05-15T18:09:18Z" cacheDuration="PT1463767758S" entityID="rsa_via_7"> <md:SPSSODescriptor AuthnRequestsSigned="true" WantAssertionsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol"> <md:KeyDescriptor use="signing"> <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <ds:X509Data> <ds:X509Certificate>YOUR-X.509</ds:X509Certificate> </ds:X509Data> </ds:KeyInfo> </md:KeyDescriptor> <md:KeyDescriptor use="encryption"> <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> <ds:X509Data> <ds:X509Certificate>YOUR-VIA-X.509</ds:X509Certificate> </ds:X509Data> </ds:KeyInfo> </md:KeyDescriptor> <md:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</md:NameIDFormat> <md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://rsa-via-hostname.com/aveksa/main" index="1" /> </md:SPSSODescriptor> <md:Organization> <md:OrganizationName xml:lang="en-US">COMPANY NAME</md:OrganizationName> <md:OrganizationDisplayName xml:lang="en-US">COMPANY NAME</md:OrganizationDisplayName> <md:OrganizationURL xml:lang="en-US">https://company.com</md:OrganizationURL> </md:Organization> <md:ContactPerson contactType="technical"> <md:GivenName>VIA Administrator</md:GivenName> <md:EmailAddress>viaadmin@company.com</md:EmailAddress> </md:ContactPerson> <md:ContactPerson contactType="support"> <md:GivenName>VIA Support</md:GivenName> <md:EmailAddress>viasupport@company.com</md:EmailAddress> </md:ContactPerson> </md:EntityDescriptor>
on Nov 18, 2015
RSA VIA does not provide a Service Provider (SP) metadata. But you can use something (SAML 2.0) like this for configuring on your federation product.
You will have to update instance specific configurations like the X.509 certificate for your VIA instance (YOUR-VIA-X.509), the VIA assertion consumer endpoint https://rsa-via-hostname.com/aveksa/main