---
title: Charmhub | Deploy Keystone Saml Mellon using Charmhub - The Open Operator Collection
description: Deploy the latest version of Keystone Saml Mellon on any cloud.
url: https://charmhub.io/keystone-saml-mellon/resources
---

# Keystone Saml Mellon

[OpenStack Charmers](https://charmhub.io/publisher/openstack-charmers "View all packages from OpenStack Charmers")

* [OpenStack Charmers](https://charmhub.io/publisher/openstack-charmers "View all packages from OpenStack Charmers")
* [Cloud](https://charmhub.io/?filter=cloud)
* [Security](https://charmhub.io/?filter=security)

Platform:

24.04

23.10

23.04

22.10

22.04

21.10

21.04

20.10

20.04

+2

yoga/stable 9ea240a

```
juju deploy keystone-saml-mellon --channel yoga/stable
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

## idp-metadata

---

### **Default resource revision for yoga/stable 213**

|  |  |
| --- | --- |
| Revision | 0 |
| Updated | 17 Apr 2019 |
| Size | 0 Bytes |
| Type | File |

Identity Provider metadata XML file that conforms to
saml-metadata-2.0-os specification. This file contains idP
identification information and its certificates with public keys
that can be used for signing and encryption on the idP side in
IDPSSODescriptor and other information which can be used on the
service provider side to interact with that idP.

---

### Release history

Developers set and validate a default resource revision for each charm revision.
To override the default resource revision (0) for yoga/stable,
you may use the following command for new deployments (this may select a resource revision that
has not been tested with this charm revision):

[Learn how to manage charm resources](https://canonical.com/juju/docs/juju-cli/latest/howto/manage-charm-resources/)

---

## sp-private-key

---

### **Default resource revision for yoga/stable 213**

|  |  |
| --- | --- |
| Revision | 0 |
| Updated | 17 Apr 2019 |
| Size | 0 Bytes |
| Type | File |

Private key used by Service Provider (mod\_auth\_mellon) to sign
and/or SAML-level (not transport-level) encryption.

---

### Release history

Developers set and validate a default resource revision for each charm revision.
To override the default resource revision (0) for yoga/stable,
you may use the following command for new deployments (this may select a resource revision that
has not been tested with this charm revision):

[Learn how to manage charm resources](https://canonical.com/juju/docs/juju-cli/latest/howto/manage-charm-resources/)

---

## sp-signing-keyinfo

---

### **Default resource revision for yoga/stable 213**

|  |  |
| --- | --- |
| Revision | 0 |
| Updated | 17 Apr 2019 |
| Size | 0 Bytes |
| Type | File |

Specifies a signing KeyInfo portion of SPSSODescriptor to be used
in Service Provider metadata. This should be an XML portion
which in the simplest case is formatted as shown below:
This fragment should contain a certificate that contains a public
key of a Service Provider in case an idP requires that SAML
requests are signed.
The term "signing certificate" is a misnomer. A signing
certificate in metadata is actually used for signature
verification, not signing. The private signing key is held
securely by the signing party (SP in this case). In a SAML
exchange an SP signs SAML messages with its private key and idP
validates them via a public key embedded in a certificate present
in the SP's metadata XML and vice versa for idP.

---

### Release history

Developers set and validate a default resource revision for each charm revision.
To override the default resource revision (0) for yoga/stable,
you may use the following command for new deployments (this may select a resource revision that
has not been tested with this charm revision):

[Learn how to manage charm resources](https://canonical.com/juju/docs/juju-cli/latest/howto/manage-charm-resources/)