Keystone Saml Mellon
- By OpenStack Charmers
- Cloud
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/edge | 91 | 25 Mar 2024 | |
yoga/stable | 99 | 30 Apr 2024 | |
zed/stable | 45 | 23 Jan 2023 | |
xena/stable | 47 | 16 Jan 2023 | |
wallaby/stable | 48 | 23 Jan 2023 | |
victoria/stable | 50 | 26 Jan 2023 | |
ussuri/stable | 63 | 01 Jun 2023 | |
train/candidate | 46 | 13 Dec 2022 | |
train/edge | 49 | 16 Jan 2023 | |
stein/candidate | 46 | 13 Dec 2022 | |
stein/edge | 49 | 16 Jan 2023 | |
rocky/candidate | 46 | 13 Dec 2022 | |
rocky/edge | 49 | 16 Jan 2023 | |
queens/candidate | 46 | 13 Dec 2022 | |
queens/edge | 49 | 16 Jan 2023 | |
2024.1/candidate | 91 | 02 May 2024 | |
2023.2/stable | 87 | 30 Nov 2023 | |
2023.1/stable | 67 | 14 Jun 2023 |
juju deploy keystone-saml-mellon --channel yoga/stable
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
sp-signing-keyinfo | File
- Revision: 0
- Updated: 17 Apr 2019
- Size: 0 Bytes
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
Revision | Date | Size |
---|---|---|
0 | 17 Apr 2019 | 0 Bytes |