Rocket.Chat Settings PageCustom Provider
This is the unique name for your application as a Service Provider (SP) for SAML. Whatever you enter here will produce a metadata XML file you will need in order to populate the metadata your IdP (Identity Provider) requires. For example, if you put ‘my-app’, then your metadata will be at:
This is the URL provided by your IdP for logging in.
IDP SLO Redirect URL
This is the URL provided by your IdP for logging out.
URL of your metadata, again, where you set Custom Provider to ‘my-app’ this will be:
This is the idp providers public certificate that is used to verify the SAML requests. Format for this is without BEGIN CERTIFICATE and END CERTIFICATE
Public Cert Contents
The public part of the self-signed certificate you created for encrypting your SAML transactions. Example of self-signed certificate on the SimpleSAMLphp website here.
The private key matching the self-signed certificate you created.
You will have to send email field in your assertion or it will not work. If the email matches existing user it will overwrite the users username with username value if that is in your assertion.
SimpleSAMLphp IdP Configuration
As a popular open source IdP, SimpleSAMLphp can be used to provide an authentication endpoint for Rocket.Chat and the built in SAML support. Assuming you have a SimpleSAMLphp IdP up and running - quickstart intructions here - you can find the metadata for the Rocket.Chat SAML Service Provider (SP) here, where ‘my-app’ is whatever you put in the ‘Custom Provider’ box in the Rocket.Chat SAML admin page:
Copy the XML on this page, open the metadata converter page in your SimpleSAMLphp admin UI (which you’ll find at
/admin/metadata-converter.php), paste the XML and submit.
Copy the resulting PHP output to the file in your SimpleSAMLphp installation under metadata:
You should now see your SP on the SimpleSAMLphp Federation page, listed as a trusted SAML 2.0 SP at: