How do we configure OverOps to allow users to login with their SAML account (authenticate) and allow access to our application (authorize) while having a different owner for all environments within OverOps?
Validate that the following listed properties are configured in the my.server.properties configuration file and the values are set accordingly.
Note: All settings must be configured in the my.server.properties file located under /<INSTALL_PATH>/takipi-server/conf/tomcat/shared/ directory.
- Enables the backend to utilize SAML SSO to authenticate users via IdP.
- Location of the metadata that is provided by the IdP. The full path to the metadata file must be provided.
- Sets the backend server to not use a domain initializer. Important to set due to all environments having different owners.
LDAP_SAML_EMAIL_FIELD_NAMES=email;mail LDAP_SAML_FIRSTNAME_FIELD_NAMES=gn;givenName;firstName LDAP_SAML_LASTNAME_FIELD_NAMES=sn;surName;lastName LDAP_SAML_PHONE_FIELD_NAMES=telephoneNumber;phone;telephone;phoneNumber
- Sets the appropriate values mapped from the users’ information within the IdP’s application to be displayed properly within OverOps. If not used, field names will be populated with the alias portion of the email address.
- Adding this parameter assigns a different separator (such as a colon [:]) to be used. If this property is not used within the properties file, a blank space will be used as the default separator between the environment and role that is passed within the SAML response.
- Assigns the attribute name that will be passed from the IdP into the OverOps application. The attribute value provided in the attribute name will need to contain the environment name and role the user is assigned to based on the groups the user has added to within their IdP. The role can be set either as Admin , Member , or Viewer . The overops-groups field name is the default SAML attribute name when this parameter is not used. Other field names that can be used are as follows:
– group, role, overops-group, groups, overops-groups, overops-role, roles, overops-roles, groups-membership
Results of the SAML Response should look like one of the following:
<saml2:Attribute Name=“overops-groups” NameFormat=“urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified”> <saml2:AttributeValue xmlns:xs="…" xmlns:xsi="…" xsi:type=“xs:string”>Environment1 Member, , Environment2 Admin</saml2:AttributeValue>
<saml2:Attribute Name=“overops-groups” NameFormat=“urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified”> <saml2:AttributeValue xmlns:xs="…" xmlns:xsi="…" xsi:type=“xs:string”>Environment1 Member</saml2:AttributeValue> <saml2:AttributeValue xmlns:xs="…" xmlns:xsi="…" xsi:type=“xs:string”>Environment2 Admin</saml2:AttributeValue>
This setup ensures that users are being authenticated via SAML and are given access to the OverOps application if the intent is to provide access to all environments and not use groups within the IdP to designate who has access to the OverOps environments.
For explanation on each of the parameters being used, please refer to the following docs:
On Premises Configuration of SAML
4.53 SAML Security Updates