Technics:SAML 2.0: Difference between revisions
Created page with "__TOC__ To use SAML, in the server folder there have to be the folder SAML2. In the folder SAML2 there have to be the following files: :* IdentityProviderMetadata.xml :* Serv..." |
No edit summary |
||
| Line 3: | Line 3: | ||
To use SAML, in the server folder there have to be the folder SAML2. In the folder SAML2 there have to be the following files: | To use SAML, in the server folder there have to be the folder SAML2. In the folder SAML2 there have to be the following files: | ||
:* IdentityProviderMetadata.xml | :* IdentityProviderMetadata.xml | ||
:* ServiceProviderCertificate.pfx | :* ServiceProviderCertificate.pfx or alternatively ServiceProviderCertificateThumbprint.txt | ||
:* ServiceProviderEntityID.txt from CoPlanner 11 Release 3 2023 | |||
==IdentityProviderMetadata.xml== | ==IdentityProviderMetadata.xml== | ||
| Line 10: | Line 11: | ||
==ServiceProviderCertificate.pfx== | ==ServiceProviderCertificate.pfx== | ||
The CoPlanner Server signs the SAML communication with that certificate. The identiy provider muss trust that certificate. | The CoPlanner Server signs the SAML communication with that certificate. The identiy provider muss trust that certificate. | ||
== ServiceProviderCertificateThumbprint.txt == | |||
It is possible to use the ServiceProviderCertificateThumbprint.txt instead of the ServiceProviderCertificate.pfx. The content of this file will be interpreted as the thumbprint to use. | |||
== ServiceProviderEntityID.txt == | |||
From CoPlanner 11 Release 3 2023 it is necessary to define the entity-ID. You can define it freely - but there are a few recommendations like it should follow the URL format. | |||
==Side Note: Creation of a certificate with OpenSSL== | ==Side Note: Creation of a certificate with OpenSSL== | ||
Latest revision as of 14:00, 16 May 2023
To use SAML, in the server folder there have to be the folder SAML2. In the folder SAML2 there have to be the following files:
- IdentityProviderMetadata.xml
- ServiceProviderCertificate.pfx or alternatively ServiceProviderCertificateThumbprint.txt
- ServiceProviderEntityID.txt from CoPlanner 11 Release 3 2023
IdentityProviderMetadata.xml
That file must include the metadata of your identity provider.
ServiceProviderCertificate.pfx
The CoPlanner Server signs the SAML communication with that certificate. The identiy provider muss trust that certificate.
ServiceProviderCertificateThumbprint.txt
It is possible to use the ServiceProviderCertificateThumbprint.txt instead of the ServiceProviderCertificate.pfx. The content of this file will be interpreted as the thumbprint to use.
ServiceProviderEntityID.txt
From CoPlanner 11 Release 3 2023 it is necessary to define the entity-ID. You can define it freely - but there are a few recommendations like it should follow the URL format.
Side Note: Creation of a certificate with OpenSSL
This sample creates the ServiceProviderCertificate.pfx with a runtime of 2000 days.
openssl req -new -newkey rsa:1024 -nodes -x509 -keyout ./temp.key -out ./temp.cert -days 2000
openssl pkcs12 -in temp.cert -inkey temp.key -export -clcerts -out ServiceProviderCertificate.pfx
