juju deploy cs:keystone-saml-mellon
Federated identity with SAML via Mellon Service Provider Read more
Discuss this charm
Share your thoughts on this charm with the community on discourse.
This subordinate charm provides a way to integrate a SAML-based identity provider with Keystone using Mellon Apache web server authentication module (mod_auth_mellon) and lasso as its dependency. Mellon acts as a Service Provider in this case and provides SAML token attributes as WSGI environment variables to Keystone which does not itself participate in SAML exchanges - it merely interprets results of such exchanges and maps assertion-derived attributes to entities (such as groups, roles, projects and domains) in a local Keystone SQL database.
In general, any identity provider that conforms to SAML 2.0 will be possible to integrate using this charm.
The following documentation is useful to better understand the charm implementation:
Use this charm with the Keystone charm, running with preferred-api-version=3:
juju deploy keystone juju config keystone preferred-api-version=3 # other settings juju deploy openstack-dashboard # settings juju deploy keystone-saml-mellon juju add-relation keystone keystone-saml-mellon juju add-relation keystone openstack-dashboard
In a bundle:
applications: # ... keystone-saml-mellon: charm: cs:~openstack-charmers-next/keystone-saml-mellon num_units: 0 options: idp-name: 'samltest' protocol-name: 'mapped' user-facing-name: "samltest.id' nameid-formats="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress" resources: idp-metadata: "./idp-metadata.xml" sp-signing-keyinfo: "./sp-keyinfo.xml" sp-private-key: "./sp-private-key.pem" relations: # ... - [ keystone, keystone-saml-mellon ] - [ openstack-dashboard, keystone-saml-mellon ] - [ "openstack-dashboard:websso-trusted-dashboard", "keystone:websso-trusted-dashboard" ]
In order to use this charm, there are several prerequisites that need to be taken into account which require certain infrastructure to be set up out of band, namely:
It is highly recommend that on the OpenStack charms side SSL/TLS be configured. We recommend deploying vault with a generated or uploaded certificate authority and relating to all OpenStack services. Optionally, ssl_ca, ssl_cert, and ssl_key can be configured on the OpenStack charms.
Several key pairs can be used in a generic SAML exchange along with certificates containing public keys. Besides the pairs used for message-level signing and encryption there are also TLS certificates used for transport layer encryption when a browser connects to a protected URL on the SP side or when it gets redirected to an idP endpoint for authentication. In summary:
- Service Provider (Keystone) TLS termination certificates, keys and CA;
- Service Provider signing and encryption private keys and associated public keys (SAML-level);
- Identity Provider TLS termination certificates, keys and CA;
- Identity Provider signing and encryption private keys and associated public keys (SAML-level).
For a successful authentication to happen the following needs to hold:
- A user agent (browser) needs to
- trust an issuer (CA) of TLS certificates of an SP used for HTTPS;
- trust an issuer (CA) TLS certificates of an idP used for HTTPS;
- be able to resolve domain names present in subject or subjAltName fields.
- An SP needs to:
- be able to verify signed SAML messages sent by an idP via public keys contained in certificates provided in the idP's metadata XML and, if SAML-level encryption is enabled, decrypt those messages;
- An idP needs to:
- be able to verify signed SAML messages sent by an SP via public keys contained in certificates provided in the SP's metadata XML and, if SAML-level encryption is enabled, decrypt those messages.
Note that this does not mean that any actual checks are performed for certificates related to SAML - only key material is used and there does NOT have to be any PKI actually in-place, not even expiration times are checked as per Mellon documentation. In that sense trust is very explicitly defined by out of band mutual synchronization of SP and idP metadata files. See SAML V2.0 Metadata Interoperability Profile (2.6.1) key processing section for a normative reference.
However, this does not mean that no PKI will be in place - TLS certificates used for HTTPS connectivity have to be verifiable by the entities that use them. With Redirect or POST binding this is mainly about user agent being able to validate SP or idP certificates - there is no direct communication between the two outside the metadata synchronization step which is performed by an operator out of band.
Additionally, for successful certificate verification clocks of all parties need to be properly synchronized which is why it is important for NTP agents to be able to reach proper NTP servers on SP and idP.
Determine the Identity Provider (idP). The idP may be public and external to your organization or a service your organization operates. It is good practice to use the URL for the idP's metadata as the unique identifier for the idP in the post-deployment configuration steps. For example https://samltest.id/saml/idp
Get the idP's metadata XML. This will be the resource file for idp-metdata.xml. The XML will be unique for each idP. See example idP metadata. The XML must be generated by your idP rather than attempting to create this document on your own.
Generate a certificate key pair for keystone as a Service Provider (SP). See
openssl documentation on how to. This certificate key pair will not be validated
so it may or may not be signed by your certificate authority.
The key PEM file is the resource file for
sp-private-key.pem. The certificate
PEM data will be placed in an XML document and will become the
sp-signing-keyinfo.xml resource file.