This plugin allows to modify the authentication process in DOTCMS using the Open SAML 3 (Security Assertion Markup Language) protocols for frontend, backend or both.
The plugin will add the user in dotcms if the user doesn't exist and for every user logging from SAML the ROLEs will be reassigned if the roles are sent by the SAML response message. In addition, a system role will be assigned to the user (SAML User role), as well as any other role defined in the configuration (for further information, refer to role.extra usage in the Configuration section)
The SAML Response should always send the user email, firstname and lastname. The roles are optional.
Before installation: Be sure your DB schema was previously initialized (dotCMS' DB tables were created). Having started the application at least once without the plugin is enough.
To use the plugin run the ./bin/deploy-plugins.sh command and restart your dotCMS instance.
For installation and configuration instructions, check the INSTALL document
For more details about properties configuration, please refer to the Configuration section
Important Considerations:
-
The plugin needs several libraries to run, all of them have been renamed with a prefix called: "opensaml". In case you need to undeploy the plugin you have to manually remove these libraries from /dotserver/tomcat-8.5.32/webapps/ROOT/WEB-INF/lib.
-
Any request from dotCMS will be redirected to the IdP Login Page, if the user is not already logged in. An exception to this rule can be set with this property access.filter.values.
-
A fallback host can be defined in order to use its configuration by default. It will only apply for those hosts whose SAML configuration field is empty. This can be set in the DOTCMS_plugin_path/conf/dotmarketing-config-ext.properties file, using the saml.fallback.site property, like this:
saml.fallback.site=saml.test.dotcms.com
In most of the cases you will need to configure just these three properties:
idp.metadata.path
In case you have a idp-metadata.xml you can get it from the classpath or file system. For the classpath, overwrite the property with the right path in your classpath. If you want to get the XML from the file system use the prefix file://.
keystore.path
Classpath or file system path for the keystore.
keystore.password
Password to access the keystore.
In this section we describe all the advance properties that can be set in your SAML configuration:
Important Considerations:
- We ship with default values for some of the properties below. You can find, add or remove those default values in the file ROOT/dotserver/tomcat-8.0.18/webapps/ROOT/WEB-INF/classes/dotcms-saml-default.properties.
- The default values will be used for each of the Sites (Hosts) SAML Field (if configured).
- You can override those values by setting key=value pairs on the SAML Field. (See How to use)
protocol.binding
By default, dotCMS uses org.opensaml.saml.common.xml.SAMLConstants.SAML2_ARTIFACT_BINDING_URI. The binding tells to the Idp how the SP is expecting the response. The default one just wait for SAMLArt parameter with the Artifact Id to resolve the artifact via Artifact Resolver. We also have support for urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST, this one expects a SAMLResponse as part of a post-back with the Assertion response.
identity.provider.destinationsso.url
URL for the login page on the Shibboleth Server. By default, it gets the url from the idp-metadata (the file provided from the Shibboleth server); in case there is not any idp-metadata you can edit this property and include the SSO url. (Note, if you set this property as well as the idp-metadata, the idp-metadata will be get by default).
service.provider.issuer
App Id for the dotCMS Service Provider. In case it is not provided, the default dotCMS site name will be set, using the https protocol. We encourage to use your url.com address, for instance: http://www.dotcms.com
assertion.customer.endpoint.url
URL used by the Idp (the Shibboleth server) to redirect to dotCMS when the login is made. We suggest to go to http://[domain]/dotsaml/login. If this value is unset, a default endpoint will be created using the service.provider.issuer and the keystore.entry.id.
logout.service.endpoint.url
URL used by the Idp (the Shibboleth server) to redirect to dotCMS when the logout is made. If this value is unset, a default endpoint will be created using the service.provider.issuer/dotsaml/logout
role.extra Custom role, set to the logged user during authentication process. This property is optional, however, in case to be included, this role must exist in dotCMS with the proper permissions (at least to Grant Users), otherwise will be ignored.
policy.allowcreate
Allows to create users that do not exist on the IdP.
We advise to not create new users on the Idp, however you can change this behavior, turning on this property.
nameidpolicy.format
SAML Name ID policy. By default we support TRANSIENT and PERSISTANCE formats, however if you want to overwrite it just add the values (comma separated). See org.opensaml.saml.saml2.core.NameIDType for more details about the valid values.
authn.comparisontype
Comparison rule used to evaluate the specified authentication methods. By default we use a MINIMUM Authorization. Possible values are:
MINIMUM
The user could be authenticated by using password or any stronger method, such as smart card for instance.
BETTER
The user must be authenticated with a stronger method than password.
EXACT
The user will be authenticated with a specific method assigned for it, for instance: if it is password, the user will be authenticated only by password.
MAXIMUM
The user will use the strongest possible method.
authn.context.class.ref
Authentication context, which could be Kerberos, Internet protocol, password, etc. See org.opensaml.saml.saml2.core.AuthnContext for more details.
By default we use: org.opensaml.saml.saml2.core.AuthnContext.PASSWORD_AUTHN_CTX
keystore.entry.id
Key entry for the keystore. By default we use SPKey, you can overwrite it if needed.
keystore.entry.password
Key entry password for the keystore. By default we use "password", it can be overwritten as well.
keystore.type
By default, java.security.KeyStore.getDefaultType() implementation is used.
signature.canonicalization.algorithm
Default value org.opensaml.xmlsec.signature.support.SignatureConstants.ALGO_ID_C14N_EXCL_OMIT_COMMENTS.
clock.skew and message.life.time
For message lifetime validation purpose. By default the clock skew is 1000 and life time 2000.
remove.roles.prefix
Depending on your Identity Providers on the IdP, the roles may be returned on the assertion with a prefix, you can change this behavior by turning on remove.roles.prefix.
build.roles
Optional key to configure the roles strategy to sync them from IDP to DOTCMS Valid values (default "all"):
- "all": Removes all user roles from DOTCMS; adds the roles to DOTCMS from IdP and role.extra (if set)
- "idp": Removes all user roles and adds the roles to DOTCMS from IdP
- "staticonly": Removes all user roles, adds roles from role.extra (if set) to DOTCMS. Ignore roles from IdP.
- "staticadd": Do not alter existing user roles, adds the roles from role.extra (if set) to DOTCMS. Ignore roles from IdP.
- "none": Do not alter any user roles on DOTCMS
attribute.email.name
By default, "mail" is the field used to fetch the user email from the Idp response.
attribute.email.allownull
Boolean value to allows to build a dummy email based on the NameID from the Idp when the email attribute from the IDP is not present. True will apply the email generation, false will throw 401 error.
attribute.firstname.name
By default "givenName" is the field used to fetch the user name from the Idp response, however if you are using another one you can overwrite it.
attribute.firstname.nullvalue
If the first name attribute is null, this value will be set instead
attribute.lastname.name
By default, "sn" is the field used to fetch the last name from the Idp response.
attribute.lastname.nullvalue
If the first name attribute is null, this value will be set instead
attribute.roles.name
By default, "authorizations" is the field used to fetch the roles/groups from the Idp response, however if you are using another one you can overwrite it.
initializer.classname
By default, dotCMS uses: DefaultInitializer. It inits the Java Crypto, Saml Services and plugin configuration details. It can be overwritten by specifying a fully qualified class name.
configuration.classname
Used to manipulate the SAML plugin configuration Default implementation: com.dotcms.plugin.saml.v3.config.DefaultDotCMSConfiguration.
idp.metadata.protocol
Attribute name used to find the Idp Information on the idp-metadata.xml (the file provided from the Shibboleth server).
Default value: "urn:oasis:names:tc:SAML:2.0:protocol"
idp.metadata.parser.classname
This class parses the idp-metadata and creates the sp-metadata from the runtime information. By default dotCMS uses DefaultMetaDescriptorServiceImpl. However, it can overwritten by adding a fully qualified class name to this property.
access.filter.values
By default, dotCMS does not filter any url, however if you want to avoid to check open saml authentication over any URL please add (comma separated) the list of urls on this property.
service.provider.custom.credential.provider.classname
Used to set custom credentials for the Service Provider. This property expects a fully qualified class name. Please see com.dotcms.plugin.saml.v3.CredentialProvider.
id.provider.custom.credential.provider.classname
Used to set custom credentials for the ID Provider. This property expects a fully qualified class name. Please see com.dotcms.plugin.saml.v3.CredentialProvider.
want.assertions.signed
Default: true. Overwrite this value if you do not want assertions signed.
authn.requests.signed
Default: true. Overwrite this value if you do not want authorization requests signed.
service.provider.custom.metadata.path
By default this is the URL to get the dotCMS Service Provider metadata: */dotsaml/metadata.xml *. However, if you want to use a different path, feel free to overwrite it.
assertion.resolver.handler.classname
By default we use this implementation: com.dotcms.plugin.saml.v3.handler.HttpPostAssertionResolverHandlerImpl.
To overwrite it, provide a fully qualified class name.
include.roles.pattern
Comma separated value, used to validate roles against the patterns provided. Only matching roles will be considered.
For instance:
"include.roles.pattern":"^www_,^xxx_"
The previous example will include only the roles from SAML that start with www_ or xxx_.
include.path.values
Comma separated values with the regex paths to be considered by the SAML plugin.
By default we include:
^/dotsaml3sp*$, ^/dotCMS/login.*$, ^/html/portal/login.*$, ^/c/public/login.*$,^/c/portal_public/login.*$,^/c/portal/logout.*$",
Use this property in case you need to filter additional paths. For instance:
"include.path.values":"^/html/portal/login.*$,^/dotCMS/login.*$,^/c/,^/admin"
logout.path.values
Comma separated values with the regex paths to be considered by the SAML plugin.
By default we include:
^/dotsaml3sp*$, ^/dotCMS/login.*$, ^/html/portal/login.*$, ^/c/public/login.*$,^/c/portal_public/login.*$,^/c/portal/logout.*$",
Use this property in case you need to add additional logout paths. For instance:
"include.path.values":"^/html/portal/logout.*$,^/dotCMS/logout.*$,^/c/"
identity.provider.destinationslo.url
This is url for the logout page on the SAML Server, by default it gets url from the idp-metadata (the file provided from the SAML server), but if it is not any idp-metadata you can edit this property and include the SLO url. (Note, if you set this property and set the idp-metadata, the idp-metada will be get by default)
verify.assertion.signature, verify.signature.profile and verify.signature.credentials
For signature verification purpose. Default value: true.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent