Author: John Dennis

# mod_auth_mellon User Guide

John Dennis
jdennis@redhat.com
version 1.2, 2017-10-6

## 1. Colophon

Author: John Dennis jdennis@redhat.com

Version: 1.2

Date: 2017-10-6

## 2. Document Conventions

Example Data used in this document

This document contains many examples of SAML data. For consistency we will use the following:

- The SP is hosted on the node `mellon.example.com`.

- The SP `MellonEndpointPath` is `/mellon`

- The SP `entityID` is `https://mellon.example.com/mellon/metadata`

- Mellon is protecting the URL location `/private` and everything under it.

- The protected resource is `/private/info.html` and hence the URL of the protected resource is `https://mellon.example.com/private/info.html`.

- The IdP is hosted on the node `rhsso.example.com`

- The IdP `entityID` is `https://rhsso.example.com:8443/auth/realms/test`

## 3. Introduction

mod_auth_mellon is an Apache (e.g. httpd) authentication module providing authentication and authorization services via SAML. Mellon plays the role of a Service Provder (e.g. SP) in SAML.

## 4. SAML Overview

SAML (Security Assert Markup Language) is a framework for exchanging security information between providers. The nonprofit OASIS consortium is responsible for defining and publishing the various SAML specifications. OASIS is an acronym for Organization for the Advancement of Structured Information Standards. All SAML specifications and errata can be found at this location:

https://docs.oasis-open.org/security/saml/v2.0/

The SAML technical committee has published the Security Assertion Markup Language (SAML) V2.0 Technical Overview. This is an excellent high level overview of SAML and worth reading to familiarize yourself with general SAML operation and terminology.

SAML is a large complex standard that currently comprises 10 individual specifications whose total content is hundreds of pages of printed material. SAML is much too large to cover in this overview, instead we will focus on the most common use of SAML, Web Single Sign-On (e.g. Web-SSO). This is target focus of mod_auth_mellon although Mellon does support other profiles as well.

SAML organizes itself into Profiles and Bindings. A cursory overview of these two concepts will help you understand SAML better and is especially important if you have to refer to any SAML specifications.

### 4.1. SAML Roles

Participants in SAML play different roles. An entity may be capable of playing more than one role however we typically only consider a single role when discussing entity behavior. The defined SAML roles are:

- Identity Provider (e.g. IdP)

- Service Provider (e.g. SP)

- Affiliation

- Attribute Authority

- Attribute Consumer

- Policy Decision Point

Of these we are only interested in Service Providers (SP) and Identity Providers (IdP). Mellon is a Service Provider because it provides a service to client. Authentication and user information is provided by an Identity Provider. The SP relies on the IdP for it’s authentication needs. In SAML literature you will often see the term attesting party or asserting party which in most contexts means an IdP because the IdP attests to, or asserts certain claims in it’s role as an authority. On the other hand Service Providers are often referred to as a relying party because it relies on the assertions provided by an authority.

### 4.2. SAML Profiles

A SAML profile defines how SAML data is conveyed using SAML Bindings on a transport to accomplish a specific task. The Web Browser SSO Profile is the best known and the one Mellon focuses on. Other profiles include Single Logout, Enhanced Client or Proxy (ECP), Identity Provider Discovery, etc.

SAML profiles are defined in the Profiles for the OASIS Security Assertion Markup Language (SAML) V2.0 specification.

### 4.3. SAML Bindings

SAML bindings define how SAML messages are mapped onto standard messaging or communication protocols. The best way to think of a SAML binding is as a transport mechanism. A key concept is that a given SAML profile may permit the same SAML message to be conveyed using variety of SAML bindings. Or by the same token a SAML profile may prohibit the use of certain SAML bindings.

SAML bindings are defined in the Bindings for the OASIS Security Assertion Markup Language (SAML) V2.0 specification.

### 4.4. SAML Messages

All SAML messages are conveyed as XML documents. A SAML XML message may be transported in a variety of mechanisms known as a SAML binding. Examples of SAML bindings include:

- query parameters of an HTTP URL.

- parameters of an HTML form.

- wrapped in a SOAP message.

The exact way a SAML interchange operates and the SAML bindings which are utilized in each step define what is called a SAML SAML profile. For example web-sso is defined by the Web Browser SSO Profile.

SAML data, and it’s XML schema are defined in the Assertions and Protocols for the OASIS Security Assertion Markup Language (SAML) V2.0 core specification.

### 4.5. SAML Web-SSO flow

The Web Browser SSO Profile is the best known SAML profile and the one Mellon focuses on. Your ability to configure Mellon and diagnose Mellon deployment issues will be greatly enhanced if you understand this flow and the two SAML messages conveyed in the flow, SAML AuthnRequest and SAML Assertion Response.

(1) HTTP Request to Service Provider

  A user agent (e.g browser) makes a request on behalf of a user for a protected resource hosted by the Service Provider (e.g. Mellon). The SP asks if there is an existing session for the user. A session is established by a prior successful SAML authentication. If a valid session exists the SP immediately grants access to the protected resource. A user session is communicated via a HTTP cookie (see Mellon Cookie). If a valid session does not exist the SP begins the authentication process.

(2) <AuthnRequest> issued by Service Provider to Identity Provider

  To authenticate the user the SP must send a `<AuthnRequest>` to an IdP. In the Web Browser SSO Profile the SP determines the IdP. The SP uses the HTTP Redirect Binding to convey the `<AuthnRequest>` to the IdP. This binding embeds the `<AuthnRequest>` in the URL query parameters of a HTTP redirect. The browser performs a redirect to the IdP which decodes the `<AuthnRequest>` embedded in the URL query parameters. The IdP also maintains session information for the user. If there is an existing valid session for the user at the IdP it immediately responds with a `<Assertion>` response unless the `<AuthnRequest>` has enabled `ForceAuthn` which requires the user to be re-authenticated. See the AuthnRequest example to better understand it’s contents and how it appears as HTTP data. Part of the data communicated along with the `<AuthnRequest>` is an item known as the RelayState. The `RelayState` is the mechanism which permits the flow to return to the original requested resource.

(3) Identity Provider identifies Principal

  If necessary the IdP authenticates the user. How the authentication is performed is not defined by SAML. Typically the IdP responds with a login page where the user enters their username and password. After successful authentication the IdP establishes a session for the user.

(4) Identity Provider issues a SAML <Response> to the Service Provider

  Assuming a valid session now exists on the IdP for the user it responds to the users browser with an `<Assertion>` using the HTTP Post Binding. The HTTP Post binding is a bit magical, you may want to review how this works in HTTP Post and Self-Posting. If a valid session could not be established for the user a failed status response is issued instead. See the Assertion example to better understand the contents of an `<Assertion>`.

(5) SP grants or denies access to the principal

  If the response does not contain a successful `<Assertion>` response the SP denies access by returning a 403 HTTP_FORBIDDEN status response. Otherwise the SP processes the `<Assertion>`. The SP may apply additional constraints on access to the protected resource (see Mellon constraints for how Mellon can apply additional authorization constraints). If the constraint check passes then the SP establishes a session for the user. Mellon associates the session information with a session ID returned in a cookie (see Mellon Cookie).

(6) SP redirects to original resource

  The SP uses the RelayState which identities the original requested resource and responds with a redirect to that URL.

(7) Browser accesses resource again

  The browser upon receiving the redirect to the original resource URL once again tries to access the resource. This time however there is a valid session established for the user as communicated in the session cookie. The SP validates the session ID which should immediately succeed. At this point Mellon informs Apache that the authentication and authorization check has succeeded for the URL.

(8) SP responds with resource

  Since the authentication and authorization checks in Apache have now passed the contents of the resource are returned to the user’s browser.

#### 4.5.1. Sessions

Sessions are maintained at both the SP and the IdP.

After an IdP successfully authenticates a user it creates a session for the user. The IdP keeps a list of every SP the user is logged into. When the user logs out the IdP sends a logout request to the SingleLogoutService endpoint of each SP. When an IdP receives a `<AuthnRequest>` from a SP it checks to see if it has an existing valid session for that user, if so it can skip authenticating the user again and instead just issue an `<Assertion>` based on the existing session. However the SP can force the IdP to always re-authenticate if it passes a `ForceAuthn` value of `True` in the `<AuthnRequest>`. The IdP may further be restricted from interacting with the if the request contains a `isPassive` value of `True`.

The IdP can inform the SP how long it wishes a SP session to be valid by passing the `SessionNotOnOrAfter` attribute in a `<AuthnStatement>`. Mellon respects the `SessionNotOnOrAfter` attribute and will limit it’s session duration based on it.

The SP also maintains a session for the user. The SP session is communicated between the browser and the SP using a cookie containing the session ID. If the SP verifies the user has an existing valid session when it receives a request it can immediately make an access decision based on the cached session information for the user.

See Mellon Sessions for more information on the particulars of how Mellon manages it sessions.

### 4.6. HTTP Post and Self-Posting

The HTTP Post Binding is used to convey an assertion back to a SP. Assertions are usually too big to embed in a URL so some other mechanism is needed to transport the `<Assertion>` response data. The data is url-form-encoded as HTTP Form. The form’s action attribute specifies the destination URL of the form data.

Where does the destination URL come from? The IdP will have loaded the SP’s metadata which defines among other things the various provider URL endpoints where SAML communication occurs. The `<Assertion>` needs to be sent to one of the SP’s AssertionConsumerService endpoints, specifically the AssertionConsumerService endpoint URL supporting the HTTP-POST binding. The SP’s AssertionConsumerService URL as read from it’s metadata is set to the action attribute of the HTTP form. The action URL is not read from any data in the <AuthnRequest>, this is one safeguard to prevent SAML messages from being sent to a unintended nefarious party. Note that many SAML bindings define a `Destination` attribute that is embedded in the SAML message. A further check compares the `Destination` attribute to the URL the message was received at, see HTTP_BAD_REQUEST - Invalid Destination on Response for a common deployment problem.

But how does the POST data as received by the user’s browser get back to the AssertionConsumerService endpoint of the SP? The form will self-post due to this:

    <body onload="document.forms[0].submit()">

As long as the user’s browser has not disabled scripts it will immediately post the form data to the AssertionConsumerService URL in the forms action attribute. If scripts have been disabled the HTML will instruct the user to click the `Submit` button to post the form data.

### 4.7. entityID

Each SAML provider (e.g. a SP or IdP) is identified by it’s `entityID`. You should think of the `entityID` as the globally unique name of the provider. The `entityID` appears in most SAML messages and in the providers metadata. This is the mechanism by which a SAML message consumer associates the SAML message with the message producers configuration properties. When a SAML provider receives a message it extracts the `entityID` from the message and then looks up the metadata belonging to that provider. The information in the providers metadata is essential in order to operate on the SAML message.

| Any mismatch between the `entityID` the producer is emitting and the consumer has loaded via the producers metadata will cause failures. A common mistake is to modify a producer’s metadata (e.g. update Mellon) but fail to reload Mellon’s metadata in the IdP.

SAML places two requirements on the `entityID`:

- It must be a URI

- It must be unique within the federation

A wise administrator will also seek to fulfill this additional requirement when choosing an `entityID`:

- It should identity the organization instead of a specific node within the organization.

When migration time arrives it is far easier to move resources around when those resources are not tied to a specific node. Thus choosing an `entityID` comprised of the organization’s domain name and a generic identifier such as `saml` would be one good approach, for example `https://bigcorp.com/saml`.

A common practice and one that recommended in the Metadata for the OASIS Security Assertion Markup Language (SAML) specification in section 4, Metadata Publication and Resolution is to use the `entityID` as a well-known-location for retrieving the provider’s metadata. In other words the `entityID` is the URL which returns the provider’s XML metadata document when an HTTP GET is performed on that URL. It is not a requirement the `entityID` be the URL for metadata download rather it is one common convention. As discussed in the SAML metadata specification other mechanisms can be established for metadata publication.

| SAML requires metadata publication to be integrity protected. A provider’s metadata is literally the keys to the provider’s kingdom as it contains the cryptographic keys used during SAML authentication as well as other vital SAML properties. It is essential to establish trust and validate the metadata. Metadata can be signed but the easiest way to assure metadata integrity and the most common is to make sure metadata is only exchanged via a secure and trusted channel, TLS provides such a mechanism. Therefore if you publish metadata (and Mellon always does irregardless whether Mellon’s metadata endpoint matches Mellon’s `entityID`) it MUST occur only over the `https` TLS scheme. Make sure your Apache configuration redirects any `http` for Mellon to `https` and that your https certificate is signed by a trusted CA such that others can properly validate your https cert. Do not use self-signed certs for your https! If you do you and you’re on a public network you’re opening yourself up to a serious security vulnerability. Note, the certs used inside the metadata can be self-signed, see Certs and Keys Inside Metadata for an explanation why. The key concept here to take away is a provider’s metadata provides the trust and is the validation mechanism used by SAML thus the integrity of the metadata is of paramount importance.

Mellon’s metadata is always published at the URL location `/$MellonEndpointPath/metadata`. See the description of MellonEndpointPath for more details on the use of MellonEndpointPath. This is why most of the tools surrounding Mellon generate an `entityID` as the concatenation of the https scheme, the hostname, the MellonEndpointPath and "metadata". Thus for example if the `MellonEndpointPath` for `bigcorp.com` was set to `saml` the `entityID` the the URL location for downloading it’s metadata would be `https://bigcorp.com/saml/metadata`. The only reason why "metadata" appears in the `entityID` is because that is Mellon’s URL endpoint for metadata publication.

### 4.8. Username, userid, SAML NameID

#### 4.8.1. Userid vs. Identity (or why userid is so last millennium)

Many people struggle with the notion of userid when working with SAML (or any other federated identity system). That’s because historically userid has been used to describe identity. The two are not the same. Identity identifies who or what something is for the purpose of authentication and authorization as well as binding attributes to that identity. In most of the literature the terms subject and principal are used interchangeably to encapsulate the concept of who or what is being identified. Although although a subject is often a person it need not be, it might also be an inanimate object. A good example of a non-human subject would be a computer service needing to be authenticated in order to perform an operation.

Userid’s grew out of the early days of computing when all computing was local and users were given accounts on a local system. The userid was how operating systems tracked who a user was, in most cases it was an integer. Clearly the integer userid only had meaning in the context of the local system. As systems became networked integer userid’s would be shared between systems but fundamentally nothing had changed, the userid was still meaningful only among a group of cooperating computers. Tools such as Yellow Pages, NIS, LDAP and Active Directory were developed to provide a centralized repository of userid’s that could be shared between cooperating networked computers. Along the way the integer userid morphed into a string often partitioned into a local part and a domain part. The domain part is used to identify the realm. Realms are nothing other than collections of unique userid’s often serving the needs of a organizational unit (e.g. company or institution).

A key concept is whoever is providing the userid, whether it be local accounts created by the host operating system or a network provider of userid’s such as NIS or LDAP each of these is an identity provider (i.e. IdP) with the userid being the key used by that specific identity provider to lookup the identity. Hence userid’s are only meaningful in the context of a specific IdP!.

By definition federated identity is amalgamation of diverse unrelated identity providers each of which utilizes it’s own userid as a key to lookup an identity. Therefore while deploying federated identity if you cling to concept of a single userid you are likely to be frustrated because you are abusing the concept.

#### 4.8.2. How SAML identifies a subject

In SAML the user name (e.g. principal or subject) is conveyed as part of the `<Subject>` element in the assertion. The subject identifier can be any one of these elements:

- `<BaseID>`

- `<NameID>`

- `<EncryptedID>`

The most common is `<NameID>` and it usually includes a `Format` attribute. If the `Format` attribute is absent then it defaults to the unspecified `Format`. The `Format` attribute tells you how to interpret the `NameID` value. For example if the subject’s `NameID` format is `urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress` you know the subject is being identified by their email address.

The currently defined `NameID` formats are:

Unspecified

  This is used when you don’t care what the `NameID` `Format` is, you’re willing to accept whatever it defaults to by the provider. (`urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified`)

Email Address

  The `NameID` is an email address as specified in RFC 2822 as a `addr-spec` in the form `local-part@domain`. No common name or other text is included and it is not enclosed in `<` and `>`. (`urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress`)

X.509 Subject Name

  The `NameID` is an X.509 subject name in form specified for the `<ds:X509SubjectName>` element in the XML Signature Recommendation. (`urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName`)

Windows Domain Qualified Name

  The `NameID` is a Windows domain qualified name. A Windows domain qualified user name is a string of the form "DomainName\UserName". The domain name and "\" separator MAY be omitted. (`urn:oasis:names:tc:SAML:1.1:nameid-format:WindowsDomainQualifiedName`)

Kerberos Principal Name

  The `NameID` is in the form of a Kerberos principal name using the format name[/instance]@REALM. (`urn:oasis:names:tc:SAML:2.0:nameid-format:kerberos`)

Persistent Identifier

  The `NameID` is a persistent opaque identifier for a principal that is specific to an identity provider and a service provider or affiliation of service providers. Opaque means you cannot (easily) map the id to a user. In many cases the persistent id is implemented as a random number or random string. Persistent means you’ll always get the exact same `NameID` for the same subject. Refer to NameIDPolicy and it’s `AllowCreate` attribute to understand if the IdP is allowed to create a persistent id for the subject if it has not already done so. (`urn:oasis:names:tc:SAML:2.0:nameid-format:persistent`)

Transient Identifier

  The `NameID` is an opaque temporary id. Opaque means you cannot (easily) map the id to a user, in many cases it’s implemented as a random number or random string. Temporary means the id is valid only in the context of the assertion response which contains it. Think of a transient id as a one-time id that cannot be used again or referred to again. (`urn:oasis:names:tc:SAML:2.0:nameid-format:transient`)

| The important concept here is SAML’s `NameID` as used to identify a subject is not the traditional userid you are probably used to. Furthermore SAML’s `NameID` may only be meaningful to the IdP which issued it.

#### 4.8.3. Burden of interpretation NameID falls to the relying party

Ultimately the SP needs to provide some sort of userid the application it is hosting can utilize. Only the application knows what it needs!

Let’s take the example of an application which wishes to identify it’s users by email address. There are two basic ways you can do this with SAML.

1. Specify a `NameIDPolicy` of `urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress` when the SP submits a `<AuthnRequest>` to the IdP. This tells the IdP you want the subject’s `NameID` to be their email address.

2. Ignore the `NameID` returned in the assertion entirely, instead use the assertion’s `email` attribute.

Solution #2 is very important to understand as it illustrates how many organizations utilize SAML, they build an identity from the attributes bound to a subject. They can use one or more attributes to build a userid meaningful to the application. They may even require the IdP return an attribute unique to the subject across a federation, in this instance all IdP’s in the federation must support that attribute (this is just one approach). The `NameID` is not utilized in solution #2 in large part because the `NameID` likely to be uniquely bound to the given IdP. This is why SAML’s transient identifiers are often used, it simply does not matter what the `NameID` is because the SP is not utilizing it therefore it can be any random one-time value.

It is also important to understand either the `NameID` or the set of attributes or both can be used to ultimately derive an identity to pass to the application.

Another approach is to utilize SAML’s persistent id with the observation the two-tuple (IdP, persistent id) always uniquely and repeatably identifies the subject. The SP can maintain a table that maps the two-tuple of (IdP, persistent id) to an application specific identity using this technique.

#### 4.8.4. How Mellon handles the NameID

Mellon extracts the `<NameID>` element from the assertion’s `<Subject>` element and sets this to `NAME_ID` attribute. If `<NameID>` is absent in the assertion you can change what Mellon considers the user name to be to another value in one of the assertions attributes if you wish. `MellonUser` names the attribute you wish to use instead.. If you want to export the username as `REMOTE_USER` so your web app can process this very common CGI variable see How to set REMOTE_USER

| Please be aware blindly exporting the SAML `NameID` to the application may or may not be appropriate for the application. See the explanation of NameID interpretation to understand the issues.

#### 4.8.5. How do you specify the NameID format in SAML?

In SAML there are 2 configuration options related to the use of `NameID`:

1. A provider declares which `NamdID` formats it supports in it’s metadata via the `<NameIDFormat>` element. The following metadata excerpt illustrates a provider which supports the `transient`, `persistent` and `X509SubjectName` formats:

    <NameIDFormat>
      urn:oasis:names:tc:SAML:2.0:nameid-format:transient
    </NameIDFormat>
    <NameIDFormat>
        urn:oasis:names:tc:SAML:2.0:nameid-format:persistent
    </NameIDFormat>
    <NameIDFormat>
        urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName
    </NameIDFormat>

2. The SP indicates to the IdP in it’s `<AuthnRequest>` what `NameID` format it wants returned via the `<NameIDPolicy>` element. The `<NameIDPolicy>` should be one of the `NameIDFormat` elements enumerated in the IdP’s metadata. The IdP is free to substitute another `NameID` format or to return an `InvalidNameIDPolicy` error status response if it can’t satisfy the request.

| Mellon defaults to a `NameIDFormat` of `transient` when it generates it’s metadata. You will need to manually edit the `NameIDFormat` in your Mellon SP metadata if you wish to use a `NameIDFormat` other than `transient`. When Mellon generates it’s `<AuthnRequest>` it selects the first `NameIDFormat` found in it’s metadata as the `NameIDPolicy`.

### 4.9. <AuthnRequest> Example

Here is an example `<AuthnRequest>` as emitted by Mellon.

    <samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
                        xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
                        ID="_59126C3306E4679F653022F0C4DA7F04" (1)
                        Version="2.0"
                        IssueInstant="2017-06-28T13:39:14Z" (2)
                        Destination="https://rhsso.example.com:8443/auth/realms/test/protocol/saml" (3)
                        Consent="urn:oasis:names:tc:SAML:2.0:consent:current-implicit"
                        ForceAuthn="false" (4)
                        IsPassive="false" (5)
                        AssertionConsumerServiceURL="https://mellon.example.com/mellon/postResponse"  (6)
                        >
      <saml:Issuer>https://mellon.example.com/mellon/metadata</saml:Issuer> (7)
      <samlp:NameIDPolicy Format="urn:oasis:names:tc:SAML:2.0:nameid-format:transient" (8)
                          AllowCreate="true"/> (9)
    </samlp:AuthnRequest>

1 | `ID`: Unique ID generated by Mellon to identify the SAML request. It will appear in the SAML response in the `InResponseTo` attribute. Used to correlate SAML request and responses.
2 | `IssueInstant`: Timestamp of when request was made
3 | `Destination`: Where this request was sent to. Used as a protection to prevent malicious forwarding of requests to unintended recipients. The recipient verifies the URL where it received the SAML request matches the `Destination`.
4 | `ForceAuthn`: If true the IdP must authenticate the principal instead of relying on an existing session for the principal.
5 | `IsPassive`: If true neither the user agent (browser) nor the IdP may take control of the user interface.
6 | `AssertionConsumerServiceURL`: Where to send the assertion response (see SP metadata AssertionConsumerService for HTTP-POST binding to see where this was defined.
7 | `Issuer`: The SP which issued the AuthnRequest. See SP metadata Issuer to see where this was defined. Also see the general description of SAML Entity ID’s
8 | `NameIDPolicy`: The SP requests the Subject returned in the assetion be identified by a transient name. See Username, userid, SAML NameID for more details.
9 | `AllowCreate`: If true then the IdP is allowed to create a new identifier for the principal.

The `<AuthnRequest>` is sent using the HTTP Redirect Binding. The above `<AuthnRequest>` appears on the wire as a URL with the SAML data embedded as query parameters. You can see the "on the wire" HTTP data for this `<AuthnRequest>` in Example On-The-Wire AuthnRequest. This illustrates the need for SAML diagnostic tools because you cannot see the `<AuthnRequest>` XML message and it’s assocated data (e.g. signature, RelayState) by looking at the HTTP protocol.

### 4.10. <Assertion> Example

This is an example of an `<Assertion>` response as generated by a Red Hat SSO server (e.g. Keycloak) in response to the above <AuthnRequest> Example

    <samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" (1)
                    xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
                    Destination="https://mellon.example.com/mellon/postResponse" (2)
                    ID="ID_d06daaaf-64ec-44d3-95a7-08da893aa9d5" (3)
                    InResponseTo="_59126C3306E4679F653022F0C4DA7F04" (4)
                    IssueInstant="2017-06-28T13:39:27.331Z" (5)
                    Version="2.0">
      <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">https://rhsso.example.com:8443/auth/realms/test</saml:Issuer> (6)
      <dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"> (7)
        <dsig:SignedInfo>
          <dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
          <dsig:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256" />
          <dsig:Reference URI="#ID_d06daaaf-64ec-44d3-95a7-08da893aa9d5"> (8)
            <dsig:Transforms>
              <dsig:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" />
              <dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
            </dsig:Transforms>
            <dsig:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256" />
            <dsig:DigestValue>V/3iYohGv2Ot7pzy6q/BfAdXgSxmdCD7K+XEmFIZlUs=</dsig:DigestValue>
          </dsig:Reference>
        </dsig:SignedInfo>
            <dsig:SignatureValue>...</dsig:SignatureValue>
            <dsig:KeyInfo>
                <dsig:KeyName>1VPndjfABB6S4lb4zwMLjBUhxfzPFnfrvNYvRgcxiUM</dsig:KeyName>
                <dsig:X509Data>
                    <dsig:X509Certificate>...</dsig:X509Certificate>
                </dsig:X509Data>
                <dsig:KeyValue>
                    <dsig:RSAKeyValue>
                        <dsig:Modulus>...</dsig:Modulus>
                        <dsig:Exponent>AQAB</dsig:Exponent>
                    </dsig:RSAKeyValue>
                </dsig:KeyValue>
        </dsig:KeyInfo>
      </dsig:Signature>
      <samlp:Status> (9)
        <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success" />
      </samlp:Status>
      <saml:Assertion xmlns="urn:oasis:names:tc:SAML:2.0:assertion" (10)
                      ID="ID_c463a141-d471-40c3-860a-6559ce0a3556"
                      IssueInstant="2017-06-28T13:39:27.331Z"
                      Version="2.0"
                      xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">
        <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">https://rhsso.example.com:8443/auth/realms/test</saml:Issuer> (11)
        <dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"> (12)
          <dsig:SignedInfo>
            <dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
            <dsig:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256" />
            <dsig:Reference URI="#ID_c463a141-d471-40c3-860a-6559ce0a3556"> (13)
              <dsig:Transforms>
                <dsig:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" />
                <dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
              </dsig:Transforms>
              <dsig:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256" />
              <dsig:DigestValue>w8bELRshtX7xHcwZCdglgfpyYBMJmVQJALPAclHHbLA=</dsig:DigestValue>
            </dsig:Reference>
          </dsig:SignedInfo>
          <dsig:SignatureValue>...</dsig:SignatureValue>
          <dsig:KeyInfo>
            <dsig:KeyName>1VPndjfABB6S4lb4zwMLjBUhxfzPFnfrvNYvRgcxiUM</dsig:KeyName>
            <dsig:X509Data>
              <dsig:X509Certificate>...</dsig:X509Certificate>
            </dsig:X509Data>
            <dsig:KeyValue>
              <dsig:RSAKeyValue>
                <dsig:Modulus>...</dsig:Modulus>
                <dsig:Exponent>AQAB</dsig:Exponent>
              </dsig:RSAKeyValue>
            </dsig:KeyValue>
          </dsig:KeyInfo>
        </dsig:Signature>
        <saml:Subject> (14)
        <saml:NameID Format="urn:oasis:names:tc:SAML:2.0:nameid-format:transient" (15)
                     xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">
                     G-803528aa-2f9e-454b-a89c-55ee74e75d1e
        </saml:NameID>
        <saml:SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:bearer">
          <saml:SubjectConfirmationData InResponseTo="_59126C3306E4679F653022F0C4DA7F04"
                                        NotOnOrAfter="2017-06-28T13:44:25.331Z"
                                        Recipient="https://mellon.example.com/mellon/postResponse"/>
        </saml:SubjectConfirmation>
        </saml:Subject>
        <saml:Conditions NotBefore="2017-06-28T13:39:25.331Z"
                         NotOnOrAfter="2017-06-28T13:40:25.331Z">
          <saml:AudienceRestriction>
            <saml:Audience>https://mellon.example.com/mellon/metadata</saml:Audience>
          </saml:AudienceRestriction>
        </saml:Conditions>
        <saml:AuthnStatement AuthnInstant="2017-06-28T13:39:27.332Z"
                             SessionIndex="9b6a46b9-28f2-4ce1-b151-713240520e5d">
        <saml:AuthnContext>
          <saml:AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:unspecified</saml:AuthnContextClassRef>
        </saml:AuthnContext>
        </saml:AuthnStatement>
        <saml:AttributeStatement> (16)
          <saml:Attribute FriendlyName="List of groups" (17)
                          Name="groups"
                          NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
            <saml:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema" (18)
                                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                 xsi:type="xs:string">ipausers</saml:AttributeValue>
            <saml:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema" (18)
                                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                 xsi:type="xs:string">openstack-users</saml:AttributeValue>
          </saml:Attribute>
          <saml:Attribute FriendlyName="email"
                          Name="email"
                          NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic"`>
            <saml:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
                                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                 xsi:type="xs:string">jdoe@music.com</saml:AttributeValue>
          </saml:Attribute>
          <saml:Attribute FriendlyName="Display Name"
                          Name="display_name"
                          NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
            <saml:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
                                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                 xsi:type="xs:string">John Doe</saml:AttributeValue>
          </saml:Attribute>
          <saml:Attribute FriendlyName="initials"
                          Name="initials"
                          NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
            <saml:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
                                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                 xsi:type="xs:string">JD</saml:AttributeValue>
          </saml:Attribute>
          <saml:Attribute FriendlyName="Last Name"
                          Name="last_name"
                          NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
            <saml:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
                                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                 xsi:type="xs:string">Doe</saml:AttributeValue>
          </saml:Attribute>
          <saml:Attribute FriendlyName="First Name"
                          Name="first_name"
                          NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
            <saml:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
                                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                 xsi:type="xs:string">John</saml:AttributeValue>
          </saml:Attribute>
          <saml:Attribute Name="Role"
                                NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
            <saml:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
                                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                 xsi:type="xs:string">uma_authorization</saml:AttributeValue>
          </saml:Attribute>
          <saml:Attribute Name="Role"
                                NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
            <saml:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
                                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                 xsi:type="xs:string">manage-account</saml:AttributeValue>
          </saml:Attribute>
          <saml:Attribute Name="Role"
                                NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
            <saml:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
                                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                                 xsi:type="xs:string">view-profile</saml:AttributeValue>
          </saml:Attribute>
        </saml:AttributeStatement>
      </saml:Assertion>
    </samlp:Response>

1 | `Response`: The `<Response>` element contains the entire SAML response which includes information concerning who issued the response, when the response was issued, optionally a signature on the response, and the actual response contents which in this case is an `<Assertion>`.
2 | `Destination`: The AssertionConsumerService endpoint where this response will be sent. The receiver will verify it arrived at this location or it will reject it.
3 | `ID`: Unique ID generated by Mellon to identify the SAML request. It will appear in the SAML response in the `InResponseTo` attribute. Used to correlate SAML request and responses.
4 | `InResponseTo`: This identifies the SAML request being responded to. It matches the `ID` attribute in the <AuthnRequest> Example. This is how SAML requests and responses are associated with one another as a pair.
5 | `IssueInstant`: Timestamp of when response was made
6 | `Issuer`: The IdP which is issuing this response. It is the entityID of the IdP as defined in the Identity Provider Metadata
7 | `Signature`: This response is signed by the IdP, the signature information is contained in this XML element.
8 | `Reference`: Identifies the XML element being signed. In this instance since the signature reference points to the top level `<samlp:Response>` the entire response is signed.
9 | `Status`: The status of the SAML response, because in this instance the status is `urn:oasis:names:tc:SAML:2.0:status:Success` the authentication was successful, if it had not been an error status would have been returned. The <Status> element is where to look for the success or failure of a SAML request.
10 | `Assertion`: This begins the assertion data, it represents the content of the SAML response.
11 | `Issuer`: The IdP which is issuing this response. It is the entityID of the IdP as defined in the Identity Provider Metadata
12 | `Signature`: The signature on the `<Assertion>`. Note this is independent of the signature on the response.
13 | `Reference`: Identifies the XML element being signed. In this instance since the signature reference points to the `<Assertion>` element because that element has the matching `ID` attribute.
14 | `Subject`: This begins the `<Subject>` element which identifies the principal being authenticated in this `<Assertion>`.
15 | `NameID`: This is where Mellon obtains the username in the assertion. Because the format is `transient` it is a random value assigned by the IdP. Note the `MELLON_NAME_ID` in the Apache environment exactly matches this. See Username, userid, SAML NameID for more details.
16 | `AttributeStatement`: This begins the set of attributes supplied by the IdP.
17 | `Attribute`: This is attribute whose `name` is groups, it is a multi-valued attribute because it contains 2 `<AttributeValue>` elements. This attribute could be written in pseudo-code as `groups=["ipausers","openstack-users"]`.
18 | `AttributeValue`: These are the values for the attribute. In this instance there are 2 values, ipausers and openstack-users.

The above `<Assertion>` response is conveyed back to the SP using the HTTP Post Binding. You may wish to review HTTP Post and Self-Posting. The "on the wire" version of this `<Assertion>` response and it and it’s associated parameter can be seen in Example On-the-Wire <Assertion> response. Once again we see the need for SAML tools because it is impossible to view the XML message and it’s associated parameters give the contents of the HTTP response.

### 4.11. SAML Endpoints

When two SAML providers communicate they must know the URL to send a given SAML message to. The set of URL’s a provider receives SAML messages is often referred to as it’s SAML endpoints. Although a SAML endpoint may appear in a SAML message this is not sufficient to identify where a response should be sent. This is because a nefarious sender could insert a bogus location in the message. To assure SAML messages are only exchanged between the expected parties the message endpoints are established outside of the message exchange via a trusted mechanism when a relationship is initially established between the two providers. Although not mandated this is almost always accomplished via the exchange of SAML metadata forming a trust relationship between the two providers. The presence of a SAML endpoint in a SAML message is typically there to validate the message against the previously established trust information. Also, as you will learn below an endpoint must be paired with a binding type which is another reason why an endpoint appearing in a SAML message is not sufficient to establish a communication pathway.

A SAML endpoint is defined by a (service,binding) pair. The service component identifies what action is hosted by this endpoint. Examples of common SAML services you are likely to encounter are:

SingleSignOnService

  Authenticate a user and establish a session for them. This is an IdP service, it’s where a SP sends it’s <AuthnRequest> message.

AssertionConsumerService

  This is where SP’s receive <Assertion> messages from an IdP in response to a <AuthnRequest> message.

SingleLogoutService

  Terminate a user’s session by logging them out. Both SP’s and IdP’s support this.

The binding component of a (service,binding) pair identifies the format of the message. Recall that SAML offers many different ways to encode the XML of a SAML message. The binding component allows the receiver to know how to decode and parse the SAML message back into an XML SAML document received at it’s service endpoint.

It’s important to understand there is no requirement for a SAML provider to locate all it’s (service,binding) pairs on distinct URL’s. It is possible to apply heuristics to a SAML message to identify the binding of the message arriving on a given URL. This allows a provider to collapse it’s set of endpoints into a smaller set of URL’s The choice of how a provider maps it’s endpoints to URL’s is entirely up to the to provider. A common mistake is to assume because one provider does it one way all providers follow the same model. The only way for you to know is to examine the providers metadata (see The Role of Metadata)

### 4.12. Relay State (How you return to the original URL)

If you’ve ever wondered how after all the redirections, posts, etc. involved in Web-SSO one finally returns back to the original requested resource you will find the answer in SAML’s `RelayState` parameter. The `RelayState` is set by the SP when it first initiates authentication. SAML requires every party that handles a SAML message to preserve the `RelayState` and ultimately return it to the original requester. Officially SAML constrains the `RelayState` to a maximum of 80 bytes and recommends it be integrity protected and not expose sensitive information because it often appears in the URL of SAML messages. This could be achieved by paring the URL with a random string, using random string as the `RelayState` and then obtaining the original URL by performing a look-up. However in practice most SAML clients set the `RelayState` to the resource URL, this is what Mellon currently does.

When your are examining SAML messages the `RelayState` will be the original URL and depending on the SAML binding it may be URL-encoded. Just be aware there is no requirement the `RelayState` be the original URL, it can be any string which the client can use to establish the context. At some future data Mellon may alter it’s `RelayState` handling.

### 4.13. The Role of Metadata

When a SAML provider needs to interact with another SAML provider they must know various properties of the foreign provider (e.g. it’s configuration). SAML provider properties are encapsulated in an XML document called SAML metadata. Examples of the provider properties conveyed in metadata include:

- entityID (the unique name of the provider)

- Organizational information

- The roles this provider offers (e.g. SP, IdP, etc.)

- endpoints for message exchange

- X509 certificates the provider uses and for what purpose

- Should messages be signed

- Attributes and attribute profiles

Typically at start-up a provider loads it’s own metadata (to configure itself) and then loads the metadata of all providers it interacts with.

The SAML metadata specification can be found here: https://docs.oasis-open.org/security/saml/v2.0/saml-metadata-2.0-os.pdf

It is vital SAML metadata be trusted. The SAML specifications do not prescribe how metadata is exchanged in a trusted fashion. Many providers offer a URL where their metadata can be downloaded from (see Mellon Endpoints. Metadata can be signed by the provider which establishes authenticity. Some SAML practitioners do not approve of downloading metadata and instead insist upon the private exchange of metadata as a means to assure the metadata is valid thus providing a higher level of trust.

Practical field experience has demonstrated the vast majority of SAML problems are due to invalid metadata. Therefore the ability to diagnose SAML problems demands the ability to read and understand SAML metadata.

To that end let’s explore the provider metadata used in our examples.

#### 4.13.1. Certs and Keys Inside Metadata

Cryptographic keys are used in SAML to sign pieces of data providing integrity protection and to encrypt data to provide confidentiality. In order for two SAML providers to successfully exchange SAML messages between themselves they must know the public keys of the other party. The provider’s public keys are declared in it’s metadata and are always encapsulated inside a `<md:KeyDescriptor>` element that defines it’s intended use (signing or encryption). Furthermore one or more of the following representations within a `<ds:KeyInfo>` element MUST be present:

- `<ds:KeyValue>`

- `<ds:X509Certificate>` (child element of `<ds:X509Data>`)

The (common) use of a `<ds:X509Certificate>` element is merely a notational convenience to encapsulate a key. SAML never utilizes any PKI information inside an X509 certificate, the only data SAML utilizes from an X509 certificate is the key material. This has several implications:

- Certs are never PKI validated.

- Certification extensions that define key usage, etc. are never checked.

- The certificate validity period is never checked, thus a cert contained in metadata never expires as a consequence of it’s certificate validity period. Instead the validity period of the key is controlled by the `<md:validUntil>` or `<md:cacheDuration>` metadata attribute associated with the key.

- Using self-signed certs used in SAML metadata is fine because the PKI data is never evaluated.

In fact extracting the key from an `<ds:X509Certificate>` element and placing it inside a `<ds:KeyValue>` element instead is semantically identical. A `<ds:X509Certificate>` element is just a container for the key, nothing more than that, certificates are used only because they are easy to generate and are readily available.

| The consequence of the above is a provider’s metadata is the trust mechanism in SAML. Any compromise of a provider’s metadata is a compromise of SAML security.

| Even though the keys and certs used inside SAML metadata for signing and encryption are not PKI validated the key and cert used to establish a TLS secure channel between SAML entities MUST be fully PKI validated using a chain all the up to a trusted CA. Do not confuse the purpose of the keys and certs used for the purpose of signing and encrypting SAML data with those used to establish secure communication, they are entirely distinct.

#### 4.13.2. Service Provider Metadata

This is an example of Mellon metadata. It is the SP metadata used in our example authentication.

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <EntityDescriptor (1)
      xmlns="urn:oasis:names:tc:SAML:2.0:metadata" (2)
      xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" (2)
      xmlns:ds="http://www.w3.org/2000/09/xmldsig#" (2)
      entityID="https://mellon.example.com/mellon/metadata"> (3)
      <SPSSODescriptor (4)
       AuthnRequestsSigned="true" (5)
       WantAssertionsSigned="true" (6)
       protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
       <KeyDescriptor use="signing"> (7)
         <ds:KeyInfo>
           <ds:X509Data>
             <ds:X509Certificate>...</ds:X509Certificate>
           </ds:X509Data>
         </ds:KeyInfo>
       </KeyDescriptor>
       <KeyDescriptor use="encryption"> (8)
         <ds:KeyInfo>
           <ds:X509Data>
             <ds:X509Certificate>...</ds:X509Certificate>
           </ds:X509Data>
         </ds:KeyInfo>
       </KeyDescriptor>
       <SingleLogoutService (9)
         Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
         Location="https://mellon.example.com/mellon/logout" />
       <SingleLogoutService (10)
         Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
         Location="https://mellon.example.com/mellon/logout" />
       <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat> (11)
       <AssertionConsumerService (12)
         index="0"
         isDefault="true" (13)
         Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
         Location="https://mellon.example.com/mellon/postResponse" />
       <AssertionConsumerService (14)
         index="1"
         Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact"
         Location="https://mellon.example.com/mellon/artifactResponse" />
       <AssertionConsumerService (15)
         index="2"
         Binding="urn:oasis:names:tc:SAML:2.0:bindings:PAOS"
         Location="https://mellon.example.com/mellon/paosResponse" />
      </SPSSODescriptor>
    </EntityDescriptor>

1 | `EntityDescriptor` is a container for all properties belonging to the entity identified by the `entityID` name. SAML metadata allows a single metadata document to describe multiple entities. In that case the top level element will be a `<EntitiesDescriptor>` element which will contain one or more `<EntityDescriptor>` elements. If the metadata describes only a single entity it is permissible to just use a `<EntityDescriptor>`
2 | XML namespace declaration. This provides an abbreviated shorthand to identify which namespace an XML element belongs to. The shorthand name is the string preceding the equals sign. If the name is absent it becomes the default namespace for XML elements which are not prefixed with a namespace. Thus for example `xmlns:ds="…​"` sets `ds` as the namespace prefix for XML digital signature elements and `<ds:KeyInfo>` means the `KenInfo` element belongs to the XML digital signature namespace because it is prefixed with `ds:`. There is no prescribed list of namespace prefixes, rather the document defines the prefix. By convention certain prefix names are commonly used. A common mistake is to assume all SAML XML documents will use the same namespace prefixes, this is not true and leads to misunderstandings and/or parsing errors.
3 | entityID, this is the unique name of the SAML provider. It must be a URI. See entityID.
4 | A provider role, in this instance the role is `SPSSODescriptor` which means it’s a Service Provider. A provider may have multiple roles therefore an entity may have more than one role elements. In our example there is only one role. See SAML Roles.
5 | `AuthnRequestsSigned`, if true then the SP will be sending a signed <AuthnRequest> to the IdP.
6 | `WantAssertionsSigned`, if true then the SP desires the IdP to sign it’s assertions. Assertions should always be signed.
7 | X509 certificate information. The `use` attribute of `signing` identifies that this certificate will be used for signing data. There may be multiple keys of this type permitting key rotation.
8 | X509 certificate information. The `use` attribute of `encryption` identifies that this certificate will be used for encrypting data. There may be multiple keys of this type permitting key rotation.
9 | SAML endpoint, logout messages using a SOAP binding are sent to this URL location.
10 | SAML endpoint, logout messages using the HTTP-Redirect binding are sent to this URL location.
11 | Zero or more `<NameIDFormat>` elements enumerate the name identifier formats supported by this entity. See Username, userid, SAML NameID for details.
12 | SAML endpoint, assertions using the HTTP-POST binding are delivered to this URL location.
13 | For indexed endpoints if `isDefault` is true then this is the default endpoint to select. If no endpoint claims to be the default then the first endpoint in the list is the default.
14 | SAML endpoint, assertions using the HTTP-Artifact binding are delivered to this URL location.
15 | SAML endpoint, assertions using the PAOS binding are delivered to this URL location. PAOS is used the the Enhanced Client or Proxy Profile (a.k.a. ECP).

#### 4.13.3. Identity Provider Metadata

This is an example of a IdP metadata as generated by a Red Hat SSO server (e.g. Keycloak). It is the IdP metadata used in our example authentication.

    <?xml version="1.0" encoding="UTF-8"?>
    <EntitiesDescriptor Name="urn:keycloak" (1)
                        xmlns="urn:oasis:names:tc:SAML:2.0:metadata" (2)
                        xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"> (2)
      <EntityDescriptor (3)
        entityID="https://rhsso.example.com:8443/auth/realms/test"> (4)
        <IDPSSODescriptor (5)
          WantAuthnRequestsSigned="true" (6)
          protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
          <KeyDescriptor use="signing"> (7)
            <dsig:KeyInfo>
              <dsig:KeyName>1VPndjfABB6S4lb4zwMLjBUhxfzPFnfrvNYvRgcxiUM</dsig:KeyName>
              <dsig:X509Data>
                <dsig:X509Certificate>...</dsig:X509Certificate>
              </dsig:X509Data>
            </dsig:KeyInfo>
          </KeyDescriptor>
        <SingleLogoutService (8)
          Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
          Location="https://rhsso.example.com:8443/auth/realms/test/protocol/saml" />
        <SingleLogoutService (9)
          Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
          Location="https://rhsso.example.com:8443/auth/realms/test/protocol/saml" />
        <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</NameIDFormat> (10)
        <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat> (10)
        <NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat> (10)
        <NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</NameIDFormat> (10)
        <SingleSignOnService (11)
          Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
          Location="https://rhsso.example.com:8443/auth/realms/test/protocol/saml" />
        <SingleSignOnService (12)
          Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
          Location="https://rhsso.example.com:8443/auth/realms/test/protocol/saml" />
        <SingleSignOnService (13)
          Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
          Location="https://rhsso.example.com:8443/auth/realms/test/protocol/saml" />
        </IDPSSODescriptor>
      </EntityDescriptor>
    </EntitiesDescriptor>

1 | `EntitiesDescriptor` is a container for multiple `<EntityDesciptor>` elements.
2 | XML namespace declaration. This provides an abbreviated shorthand to identify which namespace an XML element belongs to. The shorthand name is the string preceding the equals sign. If the name is absent it becomes the default namespace for XML elements which are not prefixed with a namespace. Thus for example `xmlns:ds="…​"` sets `ds` as the namespace prefix for XML digital signature elements and `<ds:KeyInfo>` means the `KeyInfo` element belongs to the XML digital signature namespace because it is prefixed with `ds:`. There is no prescribed list of namespace prefixes, rather the document defines the prefix. By convention certain prefix names are commonly used. A common mistake is to assume all SAML XML documents will use the same namespace prefixes, this is not true and leads to misunderstandings and/or parsing errors.
3 | `EntityDescriptor` is a container for all properties belonging to the entity identified by the `entityID` name.
4 | entityID, this is the unique name of the SAML provider. It must be a URI. See entityID
5 | A provider role, in this instance the role is `IDPSSODescriptor` which means it’s an Identity Provider. A provider may have multiple roles therefore an entity may have more than one role elements. In our example there is only one role. See SAML Roles.
6 | `WantAuthnRequestsSigned` if true indicates this IdP requires <AuthnRequests> submitted by an SP to be signed.
7 | X509 certificate information. The `use` attribute of `signing` identifies that this certificate will be used for signing data. There may be multiple keys of this type permitting key rotation.
8 | SAML endpoint, logout messages using the HTTP-POST binding are sent to this URL location.
9 | SAML endpoint, logout messages using the HTTP-Redirect binding are sent to this URL location.
10 | Zero or more `<NameIDFormat>` elements enumerate the name identifier formats supported by this entity. See Username, userid, SAML NameID for more details.
11 | SAML endpoint, <AuthnRequest> messages using the HTTP-POST binding are sent by the SP to this URL location to establish a Single Sign-On Session.
12 | SAML endpoint, <AuthnRequest> messages using the HTTP-Redirect binding are sent by the SP to this URL location to establish a Single Sign-On Session.
13 | SAML endpoint, <AuthnRequest> messages using the SOAP binding are sent by the SP to this URL location to establish a Single Sign-On Session.

## 5. Installing & Configuring Mellon

### 5.1. Installing Mellon

Mellon can be built and installed from it source code located in the mod_auth_mellon GitHub repository. However for most people the best option is to install Mellon using a pre-built package available from the package manager on your operating system. Pre-built packages relieve you of having to know the intricies of building and installing from source, track and install security fixes and track and apply bug fixes. Pre-built package also are tailored to your operating system environment often including OS specific configuration and support files deemed useful by the packaging authority.

On RHEL (CentOS)

    sudo yum install mod_auth_mellon

On Fedora

    sudo dnf install mod_auth_mellon

On Debian (Ubuntu)

    apt-get install libapache2-mod-auth-mellon

From source

    ./configure
    make
    sudo make install

| If building from source you’ll need all the necessary dependencies available at build time. Determining the exact set of dependencies and where to locate them is operating system dependent. It is assumed you have the necessary knowledge to correctly perform the requisite operations which is out of scope for this document.

### 5.2. Mellon Configuration

Once installed mod_auth_mellon does not do anything until it’s configured to operate on an URL. Mellon is configured in a manner identical to all other Apache modules, see Apache Configuration Files.

There are two independent steps necessary to enable Mellon.

1. Load the mod_auth_mellon Apache module at Apache start-up

2. Configure Mellon to operate on specific URL’s with specific SAML properties.

#### 5.2.1. Load mod_auth_mellon

To accomplish the first task of loading the mod_auth_mellon module Apache needs to execute this configuration directive:

    LoadModule auth_mellon_module modules/mod_auth_mellon.so

Different distributions may handle Apache module loading differently but as of Apache 2.4 the preferred technique is to drop a file in the `conf.modules.d` Apache directory with the above content. Apache automatically processes all `.conf` files in this directory at start-up.

| Red Hat Specific Red Hat RPM’s add the file `/etc/httpd/conf.modules.d/10-auth_mellon.conf` with the above `LoadModule` directive so there is no further action needed to load the module after the RPM is installed.

#### 5.2.2. Mellon Configuration Files

To accomplish the second task of configuring Mellon Apache will need to read Mellon configuration directives when it initializes. The preferred mechanism is to place those directives in a file located in the Apache `conf.d` directory, Apache will read all `.conf` files in this directory at start-up. Although you could place the Mellon directives in any config file a good practice to follow is keep the Mellon directives in their own file, see Mellon Configuration File for more information.

Mellon relies on SAML specific files as well, for example:

- IdP metadata file(s)

- Mellon’s SP metadata file

- Certificate and key files

Although you are free to locate these SAML specific files in the `/etc/httpd/conf.d` Apache configuration directory they are not strictly speaking Apache configuration files. Many deployments choose to locate the SAML files in a sibling directory, for example `/etc/httpd/saml2`.

| If you are running with SELinux enabled (as you should be) you may run into SELinux file permission problems if you locate files Mellon reads and writes outside the standard Apache directories because externally located files will not automatically receive the proper SELinux labels.

### 5.3. Mellon Configuration Directives

Mellon’s configuration directives are documented in Mellon’s `README` file. The README is the best place to learn and review Mellon configuration directives because it will match the installed version of Mellon.

| Red Hat Specific Red Hat RPM’s install the README file in `/usr/share/doc/mod_auth_mellon*/README`.

Mellon configuration directives are broken into 2 types:

- Module level (i.e. global values shared by each virtual server)

- Directory level (i.e. applied to directories and URL locations)

The README groups all module level directives together at the top of the file, the directory level directory level directives follow. Most users will only need to configure the directory level directives which comprise 2 basic types and are documented in Apache Core Features

<Directory> Directive

  Enclose a group of directives that apply only to the named file-system directory, sub-directories, and their contents.

<Location> Directive

  Applies the enclosed directives only to matching URL’s.

The critical thing to remember when writing and reading Mellon configuration is like all Apache directory level configuration it is hierarchical. The path portion of the URL is like a file system directory tree. If a Mellon configuration directive is not explicitly defined for a particular point in the tree the value is inherited from the closest ancestor that defines it. If no ancestor defines the value then Mellon’s default value is applied. The default value for each Mellon configuration directive is listed in Mellon’s `README` file.

### 5.4. Mellon Configuration File

For our demo example we will place these directives in the file `/etc/httpd/conf.d/demo_mellon.conf`. Let’s briefly review what the demo configuration is meant to accomplish and illustrate:

- We are protecting with SAML authentication the URL location `https://mellon.example.com/private` and everything below it in URL space.

- To eliminate redundant cut-n-paste of shared SAML directives in each protected location we gather the common Mellon directives in a location above any of the protected locations in the URL tree. This permits all protected locations to hierarchically inherit the same values from a common single set of directives.

    <Location /> (1)
        MellonEnable info (2)
        MellonEndpointPath /mellon/ (3)
        MellonSPMetadataFile /etc/httpd/saml2/demo_sp_metadata.xml (4)
        MellonSPPrivateKeyFile /etc/httpd/saml2/demo.key (5)
        MellonSPCertFile /etc/httpd/saml2/demo.cert (6)
        MellonIdPMetadataFile /etc/httpd/saml2/demo_keycloak_test_idp_metadata.xml (7)
    </Location>

    <Location /private> (8)
        AuthType Mellon (9)
        MellonEnable auth (10)
        Require valid-user (11)
    </Location>

1 | The first `Location` directive on the `/` root is simply a convenient place to locate common configuration directives that will be shared by all Mellon protected locations. In this instance it defines the metadata files and certificates and keys. It is not necessary to locate this on the `/` root URL, in fact in a real world deployment you probably will want to locate the common shared set of Mellon directives lower in the hierarchy. The only requirement is all the protected locations are positioned below it so they may inherit those values. [1]
2 | Mellon does not process any directives unless it’s enabled for that location either explicitly or via inheritance. See Mellon Modes for more details.
3 | Defines where the Mellon endpoints are located in URL space. This is a critical value to properly specify and is one of the most common Mellon configuration errors leading to a failed deployment, please refer to MellonEndpointPath to understand it’s requirements and what it influences. Also see Incorrect MellonEndpointPath for a discussion of this common error. The important thing to note in this example is the `MellonEndpointPath` is located inside the containing location directive of `/` (e.g. a child).
4 | The SAML metadata for this provider (i.e. Mellon’s metadata). This metadata plays 2 important roles. Mellon reads it at start-up to initialize itself and you provide the IdP specified in `MellonIdPMetadataFile` with this metadata. Both Mellon (the SP) and your IdP MUST have loaded exactly the same Mellon metadata in other to interoperate. Out of sync metadata is a very common deployment error. See Metadata Creation for how Mellon metadata is created. `MellonSPMetadataFile` is optional, Mellon can create it’s own metadata from it’s initial configuration parameters.
5 | The private cryptographic key used by Mellon to sign it’s SAML data. See Certs and Keys Inside Metadata for more detail.
6 | The public cryptographic key associated with the private key. This public key is embedded in Mellon’s metadata so that an IdP can validate Mellon’s signed data. See Certs and Keys Inside Metadata for more detail.
7 | The IdP used to authenticate is specified by it’s metadata file. See Obtaining IdP Metadata for how to obtain this data.
8 | This is a URL location protected by Mellon. For our example we’ve used the `/private` URL. Note this `<Location>` block is simple and does not contain many of the necessary Mellon directives, those other Mellon directives are inherited from an ancestor location, in our example `/`. The only Mellon directives in this location block are those necessary to turn on Mellon authentication. This configuration strategy permits you to define many subordinate protected locations all sharing the same common Mellon directives via inheritance.
9 | `AuthType` is a Apache directive specifying which Apache authentication module will perform the authentication for this location. Obviously we want to use Mellon.
10 | Instruct Mellon this location (and all it’s descendants) will be authenticated. See Mellon Modes.
11 | `Require` is an Apache directive that instructs Apache’s authentication and authorization sub-system must successfully authenticate the user.

#### 5.4.1. Load Your SP metadata into the IdP

After you have created your SP metadata as described in Metadata Creation you must load your metadata into the IdP referenced in your `MellonIdPMetadataFile`. How to perform the SP metadata load is specific to the IdP you’re using and you will need to consult your IdP documentation to learn the procedure.

| If you subsequently modify your SP metadata you MUST reload it into the IdP. Both your metadata and the IdP metadata must be in sync at all times. Failure to reload any modified metadata is a recipe for problems.

#### 5.4.2. Obtaining IdP Metadata

In order to Mellon to communicate with and interoperate with an IdP it must have the IdP’s metadata. You may want to refer to The Role of Metadata for a more comprehensive description. But how do you obtain the metadata belonging to the IdP? There is no fixed rule on how this is accomplished. You will have to refer to your IdP’s documentation. It may be published at a well known location (e.g. a URL) for download or there may be some other publication mechanism.

| SAML provider metadata is extremely security sensitive, it contains the cryptographic keys used to secure SAML. If you download metadata from a URL do so only over a secure channel such as https and make sure the download operation properly validates the server cert up to a CA you trust, do not trust a server offering a self-signed cert. If the obtained metadata is signed you MUST validate the signature on the metadata.

### 5.5. Mellon Modes

For any given location Mellon can be in one of 3 modes defined by the `MellonEnable` directive:

off

  Mellon will not do anything in this location. This is the default state.

info

  If the user is authorized to access the resource, then Mellon will populate the environment with information about the user. If the user isn’t authorized, then Mellon won’t populate the environment, but Mellon won’t deny the user access either.

auth

  Mellon will populate the environment with information about the user if he is authorized. If he is authenticated (logged in), but not authorized (according to the `MellonRequire` and `MellonCond` directives, then Mellon will return a 403 Forbidden error. If he isn’t authenticated then Mellon will redirect to the login page of the configured IdP.

The most common situation is to protect a specific location with Mellon authentication. This requires at a minimum these 3 directives:

        AuthType Mellon (1)
        MellonEnable auth (2)
        Require valid-user (3)

1 | This is an Apache directive that says authentication is to be performed with Mellon as opposed to another Apache authentication module.
2 | This informs Mellon it is to perform authentication as described above.
3 | This is an Apache directive that says an authentication modules must have successfully authenticated a user in order to proceed.

### 5.6. How is Mellon metadata created?

The purpose of SAML metadata is describe in The Role of Metadata. An annotated example of Mellon metadata is presented in Service Provider Metadata. There are multiple ways one can create Mellon metadata:

1. Use the `mellon_create_metadata.sh` script. The mod_auth_mellon RPM installs this script in `/usr/libexec/mod_auth_mellon/mellon_create_metadata.sh`.

2. Allow Mellon to dynamically generate it’s metadata based on it’s configuration options. The metadata can be downloaded from the `$MellonEndpointPath/metadata` URL. Mellon only self-generates it’s metadata if the `MellonSPMetadataFile` configuration parameter is not defined, otherwise if the `MellonSPMetadataFile` is defined the `$MellonEndpointPath/metadata` download URL will return the contents of the `MellonSPMetadataFile`.

3. Use a third-party tool such as `keycloak-http-client-install`.

4. Write it from scratch. (Not kidding, many provider administrators hand create and hand edit their metadata).

| Before proceeding further with Mellon metadata it is essential you understand the MellonEndpointPath.

#### 5.6.1. Using `mellon_create_metadata.sh`

`mellon_create_metadata.sh` requires two positional parameters

- entityID

- endpoint_url

The entityID is the unique name of the Mellon SP. The entityID plays an important role in SAML and you may wish to review it’s description in entityID.

The endpoint_url is the concatenation of the `https` scheme, the Mellon hostname, and the MellonEndpointPath.

Using our example data the entityID will be `https://mellon.example.com/mellon/metadata` and the endpoint_url will be `https://mellon.example.com/mellon`

    $ /usr/libexec/mod_auth_mellon/mellon_create_metadata.sh "https://mellon.example.com/mellon/metadata" "https://mellon.example.com/mellon"
    Output files:
    Private key:                              https_mellon.example.com_mellon_metadata.key
    Certificate:                              https_mellon.example.com_mellon_metadata.cert
    Metadata:                                 https_mellon.example.com_mellon_metadata.xml
    Host:                                     mellon.example.com

    Endpoints:
    SingleLogoutService (SOAP):               https://mellon.example.com/mellon/logout
    SingleLogoutService (HTTP-Redirect):      https://mellon.example.com/mellon/logout
    AssertionConsumerService (HTTP-POST):     https://mellon.example.com/mellon/postResponse
    AssertionConsumerService (HTTP-Artifact): https://mellon.example.com/mellon/artifactResponse
    AssertionConsumerService (PAOS):          https://mellon.example.com/mellon/paosResponse

The script produces 3 files containing the cert, key and metadata all prefixed with the entityID, in this example it would be:

- https_mellon.example.com_mellon_metadata.cert

- https_mellon.example.com_mellon_metadata.key

- https_mellon.example.com_mellon_metadata.xml

You will need to move these files into the Apache configuration directory and possibly rename them to something more sensible. You will references these files inside the Mellon configuration as these Mellon directives:

- `MellonSPPrivateKeyFile`

- `MellonSPCertFile`

- `MellonSPMetadataFile`

#### 5.6.2. Using Mellon to generate it’s own metadata

Mellon has the built-in capability to generate it’s own metadata as long as you provide a few necessary Mellon configuration directives.

- `MellonSPentityId`

- `MellonSPPrivateKeyFile`

- `MellonSPCertFile`

- `MellonEndpointPath` (not mandatory if you use the default)

When Mellon initializes it will check the value of the `MellonSPMetadataFile`, if it does not exist Mellon will self generate it’s own metadata. If `MellonSPMetadataFile` exists that metadata will always be used. If Mellon self generates it’s own metadata it does not write the metadata back to a file, rather it’s held in memory.

Irrespective of whether Mellon self generates it’s metadata or if it loads it from a file specified by `MellonSPMetadataFile` the metadata is made available for download at the `$MellonEndpointPath/metadata` URL. You can perform a GET on this URL to capture the SP metadata and save it in a file. It is recommended you do this as an initial configuration set-up step and then always subsequently load the metadata via the `MellonSPMetadataFile` directive. The rationale for this is you want to be sure you know what metadata Mellon is initializing with and that it identically matches what you’ve loaded into the IdP. You may also wish to customize your SP metadata by making edits to it.

#### 5.6.3. Where do the keys and certs come from?

Please refer the the Certs and Keys Inside Metadata section to understand how keys and certs are utilized inside SAML (TLS connections used for SAML communication is an entirely different matter and it is mandated keys and certs used for TLS be PKI validated). The main point to understand is even though most SAML implementations use x509 utilities to generate certs and keys SAML’s use of them does not involve PKI, only the key material is used. The consequence of this is it’s O.K. generate self-signed certs for use inside a provider’s metadata because they are not PKI validated. Many of the metadata creation tools generate a self-signed cert for use in the metadata. However it is perfectly fine to use your own key and cert instead of one generated by an installation tool. You can accomplish with Mellon either by pointing the `MellonSPPrivateKeyFile` and `MellonSPCertFile` directives at your own key and cert files and then downloading the SP metadata as described in Using Mellon to generate it’s own metadata.

#### 5.6.4. Signing metadata

SAML requires provider metadata to be integrity protected. Publishing provider metadata over a secure TLS channel goes a long way to accomplishing this goal and may be considered sufficient depending on the security requirements. SAML metadata can be integrity protected by signing the metadata with an XML signature. Some providers may require any metadata they consume be signed. Unfortunately neither Mellon nor any of the tools currently associated with Mellon have support for signing Mellon metadata. Fortunately there are a variety of tools available to sign an XML document and since SAML metadata is a normal XML document any of these tools can be used to sign the Mellon metadata.

##### Using xmlsec to sign metadata

The `xmlsec` tools are commonly available on most Linux based system. In fact the `Lasso` library which supplies Mellon with it’s SAML implementation uses the `xmlsec` library to perform all of it’s XML signing and signature verification. `xmlsec` usually ships with an `xmlsec` command line utility, this utility can perform XML signing and verification from the command line.

| `xmlsec` may be packaged under the name `xmlsec1` in your distribution. This is the case for all Red Hat distributions.

To sign Mellon metadata using `xmlsec` you need to add a signature template to the Mellon metadata. When `xmlsec` reads the input metadata it locates the empty signature template and replaces it with a processed signature. The signature template should be placed near the top of the metadata, ideally just after the `<EntityDescriptor>` element. Here is an example of a signature template:

    <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
      <SignedInfo>
        <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n"/>
        <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
        <Reference URI="">
          <Transforms>
            <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" />
          </Transforms>
          <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
          <DigestValue></DigestValue>
        </Reference>
      </SignedInfo>
    <SignatureValue />
    <KeyInfo>
      <KeyValue />
    </KeyInfo>
    </Signature>

Because the `<Reference> URI` attribute is the empty string the entire document will be signed. In order for `xmlsec` to generate a signature you will need to supply it with both the private and public key parts.

    xmlsec \\ (1)
      --sign \\ (2)
      --privkey-pem demo.key \\ (3)
      --pubkey-cert-pem demo.cert \\ (4)
      --output signed_metadata.xml \\ (5)
      metadata.xml (6)

1 | `xmlsec` command may be named `xmlsec1` on your system
2 | Perform signing
3 | Private key used for signing
4 | Public key used to verify signature (included in signature)
5 | Output file containing signed metadata
6 | Input unsigned metadata (with signature template)

To verify the signature on the command line:

    xmlsec \\ (1)
      --verify \\ (2)
      signed_metadata.xml (3)

1 | `xmlsec` command may be named `xmlsec1` on your system
2 | Perform verification
3 | Input signed metadata

### 5.7. MellonEndpointPath

Mellon reserves a number of URL’s for it’s use. Some of these URL’s are the public SAML endpoints advertised in the SP metadata. Others are for Mellon’s private use. The best way to think of these Mellon endpoints is as a way of binding a URL to a handler. When an HTTP request arrives at one of these Mellon endpoints a dedicated handler processes the request.

The way Mellon identifies a URL as being one of its endpoints is by looking at the beginning of the URL path. If everything in the path except the last path component matches the `MellonEndpointPath` then Mellon recognizes the URL as being one of it’s endpoints. The last path component is used to bind to the handler.

Let’s use an example. If the `MellonEndpointPath` is `/foo/bar` then any URL with the `/foo/bar/xxx` form will be handled by Mellon’s xxx handler.

Mellon enforces 2 strict requirements on the `MellonEndpointPath`.

- The path must be an absolute path from the root of the web server.

- The directory must be a sub-directory of the Mellon `<Location>` directive that defines it. The reason for this is simple. Mellon ignores locations which are not configured for Mellon. Therefore for Mellon to respond to a request on one of it’s SAML endpoints has to be inside a directory Mellon is watching.

### 5.8. Mellon Endpoints

Mellon endpoints are hung off of the MellonEndpointPath. Mellon reserves a number of URL’s for it’s use. Some of these URL’s are the public SAML endpoints advertised in the SP metadata. Others are for Mellon’s private use. The best way to think of these Mellon endpoints is a way of binding a URL to a handler. When an HTTP request arrives at one of these Mellon endpoints a dedicated handler processes the request.

The current list of Mellon endpoints (handlers) is:

postResponse

  The AssertionConsumerService endpoint using the SAML HTTP-POST binding.

artifactResponse

  The AssertionConsumerService endpoint for SAML artifacts. SAML artifacts provide an indirect method to convey data. An artifact is an identifier that points to data. Requesting data using the artifact identifier returns the associated data.

paosResponse

  The AssertionConsumerService endpoint using the SAML PAOS binding.

login

  Mellon internal endpoint used to start the authentication process with an IdP. Any request whose URL needs authentication is redirected here to start the login process.

logout

  The SingleLogoutService SAML endpoint.

metadata

  A HTTP GET request on this endpoint will return the SP’s metadata.

repost

  Mellon internal endpoint which replays POST data from the original request.

auth

  Mellon internal endpoint retained for backwards compatibility.

probeDisco

  IdP probe discovery service endpoint. See "Probe IdP discover" in the Mellon README for more information.

### 5.9. Mellon Session

SAML sessions are described in Sessions.

For each successfully authenticated user Mellon maintains a session. Mellon allocates a unique ID for the session when it is created. The Mellon session ID is sent to the user’s browser in a Mellon Cookie. The Mellon Cookie is sent back to Mellon in every request the browser makes to the SP. Mellon uses the session ID to look-up the session data for the user. Internally Mellon calls session data cache data (this is subject to change).

At the time of this writing Mellon session data is local to one Apache server (which may have multiple worker processes sharing data in shared memory). This has consequences for High Availability (e.g. HA) deployments which may be running multiple Apache servers on different nodes behind a load balancer, see Load balancer proxy persistence for detailed information on this issue.

Mellon limits the duration of a valid session by the length of time defined in the `MellonSessionLength` directive. Currently the default is 86400 seconds which is 24 hours.

The IdP can inform the SP how long it wishes a SP session to be valid by passing the `SessionNotOnOrAfter` attribute in a `<AuthnStatement>`. Mellon respects the `SessionNotOnOrAfter` attribute and will limit it’s session duration based on it. Thus the validity period for a Mellon session is the lesser of the `MellonSessionLength` or the optional IdP `SessionNotOnOrAfter` attribute if the IdP supplied it.

### 5.10. Mellon Cookie

Mellon Session information is communicated via a cookie. The cookie name defaults to `mellon-cookie` but may be changed via the Mellon directive `MellonVariable`. Mellon always forms the cookie name by appending the value of `MellonVariable` to the string `mellon-` to prevent name collisions. Thus the actual default value of `MellonVariable` is `cookie`.

When Mellon first begins the authentication process it sets the mellon cookie value to `cookietest`. The primary purpose of the `cookietest` value is to confirm cookies are properly returned by the browser, Mellon will not work correctly unless cookies are enabled. The `cookietest` value also serves as a temporary value indicating an authentication flow is in progress but has not yet completed.

After Mellon successfully authenticates a user it establishes a session for the user and generates a unique session ID which it sets as the value of the Mellon cookie. When Mellon receives a request for a protected resource it looks for the Mellon cookie in the HTTP request headers. Mellon then uses the Mellon cookie value as a session ID and attempts to look-up that session using that ID. If the session is found and it’s remains valid Mellon immediately grants access. A Mellon session will expire, see Mellon Session for information concerning session lifetime.

## 6. Working with SAML attributes and exporting values to web apps

When you receive a SAML assertion authenticating a subject the assertion will likely include additional attributes provided by the IdP concerning the subject. Examples include the user’s email address or the groups they are a member of. You may wish to review the assertion example and look for `<saml:Attribute>` and `<saml:AttributeValue>` elements to see how the IdP communicates these attributes. There is no fixed set of attributes returned by an IdP, it is entirely IdP dependent. You will either have to review your IdP’s documentation or examine a returned assertion to determine the possible attributes. See Inspect SAML messages for the various ways you can examine the contents of a returned assertion.

Mellon communicates it’s results via Apache environment variables. For every attribute received in the assertion Mellon will insert an Apache environment variable. You have some flexibility on how Mellon adds these environment variables which derive from the assertion attributes.

- Attributes can be multi-valued. `MellonMergeEnvVars` controls whether each value is added to the environment by appending an index to the attribute name or whether the values are listed together under the bare attribute name with each value separated by a separator character. See Handling multiple attribute values.

- Attribute names can be mapped from the name as it appears in the assertion to a name of your choosing when it is placed in the Apache environment. This is controlled by `MellonSetEnv` and `MellonSetEnvNoPrefix` directives. The distinction is `MellonSetEnv` always prepends the `MELLON_` prefix to the environment variable name to help to prevent name collisions. The `MellonSetEnvNoPrefix` directive also remaps the assertion name to a name of your choosing but it omits prepending the environment variable name with `MELLON_`. See Map assertion attribute name to different Apache environment variable name

Using the assertion example Mellon places these environment variables in the Apache environment. See Handling multiple attribute values for an explanation of `MellonMergeEnvVars` and it’s effect.

MellonMergeEnvVars Off

    MELLON_NAME_ID: G-803528aa-2f9e-454b-a89c-55ee74e75d1e
    MELLON_NAME_ID_0: G-803528aa-2f9e-454b-a89c-55ee74e75d1e
    MELLON_groups: ipausers
    MELLON_groups_0: ipausers
    MELLON_groups_1: openstack-users
    MELLON_email: jdoe@music.com
    MELLON_email_0: jdoe@music.com
    MELLON_display_name: John Doe
    MELLON_display_name_0: John Doe
    MELLON_initials: JD
    MELLON_initials_0: JD
    MELLON_last_name: Doe
    MELLON_last_name_0: Doe
    MELLON_first_name: John
    MELLON_first_name_0: John
    MELLON_Role: uma_authorization
    MELLON_Role_0: uma_authorization
    MELLON_Role_1: manage-account
    MELLON_Role_2: view-profile
    MELLON_IDP: https://rhsso.example.com:8443/auth/realms/test
    MELLON_IDP_0: https://rhsso.example.com:8443/auth/realms/test

### 6.1. Handling multiple attribute values

If an attribute has multiple values, then they will be stored as

    MELLON_<name>_0 value0
    MELLON_<name>_1 value1
    MELLON_<name>_2 value2
    ...

Since Mellon doesn’t know which attributes may have multiple values, it will store each attribute at least twice. For example:

    MELLON_<name> value0
    MELLON_<name>_0 value0

In the case of multivalued attributes `MELLON_<name>` will contain the first value.

If `MellonMergeEnvVars` is enabled multiple values of attributes will be stored in a single environment variable separated by the `MellonMergeEnvVars` separator which defaults to the semicolon. You can override the default separator by supplying it as the second option to the `MellonMergeEnvVars` directive.

Thus the above environment variable list would be this if `MellonMergeEnvVars` was on and the separator was set to the semicolon.

MellonMergeEnvVars On ;

    MELLON_NAME_ID: G-803528aa-2f9e-454b-a89c-55ee74e75d1e
    MELLON_groups: ipausers;openstack-users
    MELLON_email: jdoe@music.com
    MELLON_display_name: John Doe
    MELLON_initials: JD
    MELLON_last_name: Doe
    MELLON_first_name: John
    MELLON_Role: uma_authorization;manage-account;view-profile
    MELLON_IDP: https://rhsso.example.com:8443/auth/realms/test

### 6.2. Map assertion attribute name to different Apache environment variable name

Sometimes the web app is expecting a specific name for a SAML attribute but your IdP has sent that attribute under a different name. You can rename any assertion attribute using the `MellonSetEnv` and `MellonSetEnvNoPrefix` directives. These allow you to rename an assertion attribute to a name of your choosing. The `MellonSetEnv` directive follows the same convention as all other assertion attributes added by Mellon in that it always prefixes the environment variable name with `MELLON_` to help avoid name collisions in the Apache environment. However sometimes you do not want the `MELLON_` prefix added and instead you want to use exactly the environment variable name as specified., `MellonSetEnvNoPrefix` serves this role.

To illustrate let’s look at an example. Suppose your web app is expecting an attribute which is the user’s last name, specifically it wants this attribute to be called `REMOTE_USER_LASTNAME`. However your IdP sends this attribute as `sn`. `sn` is typically used in LDAP directories as an attribute name for surname, or equivalently the user’s last name. To map the `sn` assertion attribute name to the Apache environment variable name of `REMOTE_USER_LASTNAME` you would do this:

    MellonSetEnvNoPrefix REMOTE_USER_LASTNAME sn

Also see How to set REMOTE_USER for an example of setting the `REMOTE_USER` environment variable using `MellonSetEnvNoPrefix`.

### 6.3. Using Mellon to apply constraints

SAML attributes can be used for more than exporting those values to a web app. You can also utilize SAML attributes to control whether Mellon authentication succeeds (a form of authorization). So even though the IdP may have successfully authenticated the user you can apply addition constraints via the `MellonCond` directive. The basic idea is each `MellonCond` directive specifies one condition that either evaluates to `True` or `False`. Multiple conditions can be joined by logical operators. You can also specify case insensitive matching, substring matching, regular expression matching, substitute values, and use regular expression back references. All `MellonCond` conditions must evaluate to `True` for the condition check to succeed (logical conjunction) unless you use the `OR` option flag.

The directive is specified as:

    MellonCond attr_name value [options]

The 1st `attr_name` parameter is the name of the SAML assertion attribute the condition applies to. If an attribute with this name is found it’s value is retrieved and becomes the data the condition is evaluated against. If `attr_name` is not found the condition evaluates to `False`.

The 2nd value parameter is the value applied to the attribute value. For example when matching is performed the `value` parameter is searched for inside the attribute’s value.

The `value` parameter may contain format specifiers which are substituted prior to performing an operation on the value. Format specifiers always begin with the `%` character. Here are the valid format specifiers:

%n

  Regular expression backreference. Regular expressions may contain multiple sub-matches (often referred to as a regular expression group). To refer to a specific sub-match in the regular expression pattern use a digit between 0 and 9 as `%n`. This only works if a prior condition had specified the [`REG,REF]` flags, otherwise there would be no backreference to refer to.

%{num}

  Same as `%n` but permits a number greater than 9.

%{ENV:x}

  Substitute the Apache environment variable `x`. If the environment variable does not exist substitute the empty string instead.

%%

  Quote a `%` to prevent it from being interpreted as a the beginning of a format specifier.

The 3rd `[options]` parameter is optional and if specified is a comma separated list of option flags enclosed in square brackets. The set of option flags includes:

OR

  If this MellonCond evaluated to false, then the next one will be checked. If it evaluates to true, then the overall check succeeds.

NOT

  Invert the result of the condition check. If the condition evaluated to `True` it becomes `False`, likewise if the condition evaluated to `False` it become `True`.

NC

  Case insensitive matching. Ignore case differences when performing any match operation.

SUB

  Substring match. If value is included anywhere in the attribute value as a substring the condition evaluates to `True`, `False` otherwise. If `SUB` is not specified then the condition value and attribute value must match in it’s entirety.

REG

  Regular expression match. The value is interpreted as a regular expression. If the regular expression is found in the attribute value the condition evaluates to `True`, `False` otherwise.

REF

  Used with REG, track regular expression back references, So that they can be substituted in an upcoming `MellonCond` directive.

MAP

  Use mapped name. Instead of looking up the attribute name in the set of attributes returned in the assertion use the mapped name specified by either `MellonSetEnv` or `MellonSetEnvNoPrefix` instead. If the mapped name is not found then fallback to using the name in the assertion’s set of attributes.

Here is a simple example illustrating how one might utilize `MellonCond`. Suppose we only want to allow members of the group `openstack-users` to have access. Our IdP has provided us with the list of groups the user is a member of in the `groups` SAML attribute. We need to instruct Mellon to only accept an assertion if `openstack-users` appears as one of the `groups` attribute values. This can be accomplished like this:

    MellonCond groups openstack-users

If `openstack-users` does not appear in the as one of the `groups` attribute values the check will fail. The check will also fail if the `groups` attribute is not defined in the assertion.

### 6.4. How to set REMOTE_USER

Mellon stores the authenticated user’s name in the attribute `NAME_ID` (see Username, userid, SAML NameID). If you want to export the username as `REMOTE_USER` so your web app can process this very common CGI variable this can easily be accomplished with `MellonSetEnvNoPrefix` like this:

    MellonSetEnvNoPrefix REMOTE_USER NAME_ID

## 7. Deployment Considerations

### 7.1. Apache Servername

When Mellon is running behind a load balancer, SSL terminator or in a Apache virtual host there is the opportunity for Mellon to identify itself incorrectly. If Mellon does not identify itself identically to what appears in the matching metadata various SAML security checks will fail as well as the ability to communicate on the defined SAML Endpoints.

At run time Mellon asks Apache what scheme, host and port it’s running under. Mellon uses this information to build URL’s. When Mellon is running in a simple configuration directly connected to the internet Apache typically gets this information correctly from the environment. However when Apache is behind some type of proxy such as a load balancer then there is a distinction between what clients see as the front end and what Mellon sees when it’s running as a backend server. The trick is to make Mellon believe it’s running as the front end so that it matches the client’s view. You may wish to refer to Load Balancer Issues for more information.

Load balancers partition their view between front end and back end.

front end

  What the client connects to. It’s the public scheme, hostname, and port.

back end

  The back end server is where Mellon runs. It will definitely have a different hostname than the front end and will likely also have a different scheme and port as well.

When a HTTP request arrives at the front end most load balancers will terminate the SSL connection. This changes the scheme from `https` to `http`. The load balancer will select a backend server to forward the request to. The backend server will have a different hostname and possibly a different port. Mellon needs to see the HTTP request as it appeared on the front end instead of how the request appears to the backend server where Mellon is running.

The host and port appear in several contexts:

- The host and port in the URL the client used

- The host HTTP header inserted into the HTTP request (derived from the client URL host).

- The hostname of the front facing proxy the client connects to (actually the FQDN of the IP address the proxy is listening on)

- The host and port of the backend server which actually handled the client request.

- The virtual host and port of the server that actually handled the client request.

It is vital to understand how each of these is utilized otherwise there is the opportunity for the wrong host and port to be used with the consequence the authentication protocols may fail because they cannot validate who the parties in the transaction are and whether the data is carried in a secure transport.

Let’s begin with the backend server handling the request because this is where the host and port are evaluated and most of the problems occur. The backend server need to know:

- The URL of the request (including host & port)

- It’s own host & port

Apache supports virtual name hosting. This allows a single server to host multiple domains. For example a server running on example.com might service requests for both bigcorp.com and littleguy.com. The latter 2 names are virtual host names. Virtual hosts in Apache are configured inside a server configuration block, for example::

    <VirtualHost>
      ServerName bigcorp.com
    </VirtualHost>

When Apache receives a request it deduces the host from the `HOST` HTTP header. It then tries to match the host to the `ServerName` in it’s collection of virtual hosts.

The Apache `ServerName` directive sets the request scheme, hostname and port that the server uses to identify itself. The behavior of the `ServerName` directive is modified by the Apache `UseCanonicalName` directive. When `UseCanonicalName` is enabled Apache will use the hostname and port specified in the `ServerName` directive to construct the canonical name for the server. This name is used in all self-referential URLs, and for the values of SERVER_NAME and SERVER_PORT in CGIs. If `UseCanonicalName` is `Off` Apache will form self-referential URLs using the hostname and port supplied by the client, if any are supplied.

If no port is specified in the `ServerName`, then the server will use the port from the incoming request. For optimal reliability and predictability, you should specify an explicit hostname and port using the `ServerName` directive. If no `ServerName` is specified, the server attempts to deduce the host by first asking the operating system for the system hostname, and if that fails, performs a reverse lookup on an IP address present on the system. Obviously this will produce the wrong host information when the server is behind a proxy because the backend server is not what is seen on the frontend by clients therefore use of the `ServerName` directive is essential.

| Browsers will strip standard port 80 for HTTP and port 443 for HTTPS from the network location in a URL. For example if you specify a URL like this `https://example.com:443/some/path` the URL which will placed on the wire will be `https://example.com/some/path` without the standard port. Since Mellon and most SAML providers validate URL’s by simple string comparison including a standard port in a URL will cause URL matching to fail because one URL will have the port in it and the other URL won’t.

The Apache ServerName doc is very clear concerning the need to fully specify the scheme, host, and port in the `Server` name directive when the server is behind a proxy, it states:

> Sometimes, the server runs behind a device that processes SSL, such as a reverse proxy, load balancer or SSL offload appliance. When this is the case, specify the https:// scheme and the port number to which the clients connect in the ServerName directive to make sure that the server generates the correct self-referential URLs.

### 7.2. Load Balancer Issues

High Availability (HA) deployments often run their services behind a load balancer. By far the most popular load balancer is HAProxy. As a consequence we will use HAProxy examples in this document, other load balancers behave in a similar fashion to HAProxy and you can extrapolate the HAProxy information to them.

#### 7.2.1. Server Name

Because backend servers do not self-identify with the same front end public address it is vital you force those Apache servers to identify with the public address, this issue is described in Apache Servername. The reason for this is because the SAML protocols require URL’s to match what is in a SAML providers metadata. If you allow a backend server to self-identify the URL’s exchanged in the protocols will not match and you will encounter an error, see HTTP_BAD_REQUEST - Invalid Destination on Response.

#### 7.2.2. Load balancer proxy persistence

In an HA deployment multiple backend servers run on distinct nodes and cooperate to mitigate the load that might be placed on a single (front end) server. Because the backend servers are independent they do not share state with any other backend server unless something has explicitly be done to share state. HTTP is technically a stateless protocol which makes web traffic ideally suited for a HA deployment, each backend server can be ignorant of any other HTTP request. However in practice HTTP is stateful by virtue of cookies. Authentication protocols are good examples of HTTP transactions that require saved state, in particular Mellon sessions.

| At the time of this writing Mellon has no support for sharing session data between independent Apache servers. The consequence of this is Mellon will not work correctly unless the same Apache server consistently handles a users HTTP traffic.

HAProxy has two different mechanisms to bind HTTP traffic to one server, affinity and persistence. This article provides an excellent overview of the distinction between the two and how to implement it "load balancing, affinity, persistence, sticky sessions: what you need to know"

What is the difference between Persistence and Affinity? Affinity is when information from a layer below the application layer is used to pin a client request to a single server. Persistence is when application layer information binds a client to a single server sticky session. The main advantage of persistence over affinity is it is much more accurate.

Persistence is implemented though the use of cookies. The HAProxy `cookie` directive names the cookie which will be used for persistence along with parameters controlling it’s use. The HAProxy `server` directive has a `cookie` option that sets the value of the cookie, it should be set to the name of the server. If an incoming request does not have a cookie identifying the backend server then HAProxy selects a server based on it’s configured balancing algorithm. HAProxy assures the cookie is set to the name of the selected server in the response. If the incoming request has a cookie identifying a backend server then HAProxy automatically selects that server to handle the request.

To enable persistence in the backend server block of the `/etc/haproxy/haproxy.cfg` configuration this line must be added::

    cookie SERVERID insert indirect nocache

This says `SERVERID` will be the name of our HAProxy persistence cookie. Then we must edit each `server` line and add `cookie <server-name>` as an additional option. For example::

    server server-0 cookie server-0
    server server-1 cookie server-1

Note, the other parts of the server directive have been omitted for clarity.

| The Mellon session cookie and the HAProxy server persistence cookie are entirely separate, do not confuse them. The HAProxy server persistence cookie identifies the backend server which issued the Mellon cookie.

For Mellon to work correctly all user requests must be handled by the same backend server that issued the Mellon cookie in the first place.

### 7.3. Forwarded HTTP Headers

When proxies are in effect the `X-Forwarded-\*` HTTP headers come into play. These are set by proxies and are meant to allow an entity processing a request to recognize the request was forwarded and what the original values were before being forwarded.

A common HAProxy configuration sets the `X-Forwarded-Proto` HTTP header based on whether the front connection utilized SSL/TLS or not via this configuration::

    http-request set-header X-Forwarded-Proto https if { ssl_fc }
    http-request set-header X-Forwarded-Proto http if !{ ssl_fc }

To make matters interesting core Apache does not interpret this header thus responsibility falls to someone else to process it. In the situation where HAProxy terminates SSL prior to the backend server processing the request the fact the `X-Forwarded-Proto` HTTP header is set to https is irrelevant because Apache does not utilize the header when an extension module such as Mellon asks for the protocol scheme of the request. This is why it is essential to have the `ServerName` directive include the `scheme:://host:port` and to have `UseCanonicalName` enabled otherwise Apache extension modules such as Mellon will not function properly behind a proxy.

But what about web apps hosted by Apache behind a proxy? It turns out it’s the web app (or rather the web app framework) responsibility to process the forwarded header. Thus apps handle the protocol scheme of a forwarded request differently than Apache extension modules do.

The critical thing to note is is that Apache extension modules and web apps process the request scheme of a forwarded request differently demanding both the `ServerName` and `X-Forwarded-Proto` HTTP header techniques be utilized.

## 8. Gathering run-time information

### 8.1. Apache log files

Mellon writes messages to the Apache server error log file. Depending on your Apache configuration those message might appear in either `/var/log/httpd/error_log` or `/var/log/httpd/ssl_error_log`. You can turn up the verbosity of the messages by modifying the Apache `LogLevel`, for example:

    LogLevel debug

| Mellon’s use of standard Apache logging is limited, see Mellon Diagnostics for a much better was to capture Mellon run time information.

### 8.2. Trace SAML flow

Since you’re most likely using the SAML Web-SSO profile which is entirely browser based you can use any of the browser tools to watch HTTP requests and responses. The Firefox web browser provides the FireBug add-on and the Chrome browser offers Developer Tools. Each of these browsers also have additional add-ons to display SAML messages, see Inspect SAML messages.

| The easiest and most complete way to trace HTTP requests and responses during SAML flow, capture SAML messages and examine how Mellon processes a SAML message is to use Mellon Diagnostics.

### 8.3. Inspect SAML messages

There are many times when you need to see the content of a SAML message. Perhaps you don’t know what attributes your IdP is returning in an assertion. Or the SAML transaction is failing for some reason and you need to diagnose why. In such cases being able to see the contents of the SAML messages can be immensely helpful.

Examining the on-the-wire SAML data is seldom useful, even when it’s contained in otherwise visible HTTP data elements such as query parameters, post data, etc. This is because the various SAML bindings encode the message in different ways. It may break the message into independent components which need to be reassembled at the receiving end or it may encode the data in a variety of formats which need to be decoded to recover the original message content. It’s best to use SAML aware tools to examine SAML messages because they know how to decode and reassemble the raw SAML data into the final SAML message the receiver evaluates.

| The easiest and most complete way to capture SAML messages and examine how Mellon processes a SAML message is to use Mellon Diagnostics. If your version of Mellon supports diagnostics you may wish to skip to this section.

The Web-SSO SAML profile is by far the most commonly used. Because all SAML messages transit though the browser in Web-SSO it is possible to write a browser extension to capture and decode the SAML messages exchanged between the SP and IdP.

#### 8.3.1. Firefox SAML Tracer

The Firefox SAML Tracer Add-On will display decoded SAML messages used during single sign-on and single logout. SAML Tracer is not capable of decrypting an encrypted IdP response because it does not have access to the IdP’s public encryption key contained in the IdP’s metadata, see If the IdP response is encrypted for how to deal with this issue.

To use SAML Tracer you must first install the add-on. Then each time you want to use SAML Tracer you will need to go to the Firefox menu and select the SAML Tracer option. This will bring up a separate Firefox window which looks like this:

The SAML Tracer window is divided into two panes, a list of HTTP requests in the top pane and detailed information on the selected request in the bottom window.

SAML Tracer examines each HTTP request and response and if it detects it is a SAML message it flags the request in the request list window at the top with a "SAML" icon.

In the detail pane are different tabs which show you the request/response information in different views. In order to view the decoded SAML message you need to make the `SAML` tab active. The `Parameters` tab shows you the query parameters (either URL or POST), SAML messages are usually transported in HTTP parameters so this is where you can see the raw SAML data before being decoded into a complete SAML message. The `http` tab shows you the HTTP headers associated with the HTTP request/response.

#### 8.3.2. Chrome, SAML Chrome Panel

The Chrome Web browser offers several add-ons to display SAML messages. The most commonly used is SAML Chrome Panel. SAML Chrome Panel integrates with the Chrome developer tools.

Here is an example of the SAML Chrome Panel in the developer tools panel.

#### 8.3.3. If the IdP response is encrypted

Data in a SAML response may be encrypted for confidentiality (usually encryption is not needed because SAML transactions should be occurring over a secure TLS channel). Decrypting the data requires access to the IdP’s public encryption key contained in it’s metadata. Most SAML browser tools do not support decryption. If you discover your tool is showing you encrypted data you have a few options:

- Disable encryption at the IdP. See your IdP’s documentation on how to enable/disable encryption.

- Use Mellon Diagnostics. The diagnostics support in Mellon operates after the SAML message is decoded from it’s SAML binding transport and after it’s been decrypted into a final plaintext SAML XML document. Most people will find Mellon diagnostics to be the easiest and most complete capture of SAML data and Mellon’s processing of it.

### 8.4. Inspecting Mellon environment variables

Recall that Mellon communicates with web apps by inserting Apache environment variables into the Apache environment. While diagnosing problems or when initially setting up your Mellon deployment it can be very useful to see the contents of the Apache environment. The typical way this is done is to substitute the resource Mellon is protecting with a script that dumps the environment it received. So instead of getting back the resource after Mellon successfully authenticates the script runs and returns a page listing the environment variables. Once you’ve collected this information you need to remove the script from the protected URL so the protected resource will be returned instead of a data dump.

If your installed version of Mellon includes support for Mellon Diagnostics there is no need to alter your protected resource in order to get an environment variable dump. The diagnostics log includes a dump of the complete Apache environment at the end of each response. This is a much easier and more complete solution than substituting a script for your protected resource.

#### 8.4.1. Python WSGI Environment Dump

Create a script with the following content:

    import pprint
    import webob
    import webob.dec

    @webob.dec.wsgify
    def application(req):
        return webob.Response(pprint.pformat(req.environ),
                              content_type='application/json')

Placing the above script in the Apache `cgi-bin` directory is a good idea, we’ll name this script 'dump-env'

Add a `WSGIScriptAlias` directive to your Apache configuration so that it runs the above script when the protected resource URL is requested. For example:

    WSGIScriptAlias "/private/info.html" "/var/www/cgi-bin/dump-env"

#### 8.4.2. PHP Environment Dump

    <?php
    header('Content-Type: text/plain');

    foreach($_SERVER as $key=>$value) {
      if(substr($key, 0, 7) == 'MELLON_') {
        echo($key . '=' . $value . "\r\n");
      }
    }
    ?>

### 8.5. Mellon Diagnostics

When something goes wrong with your Mellon deployment experience has been shown it can be frustratingly difficult to gather sufficient information to diagnose the problem. Often you will need access to the following pieces of information:

- Mellon configuration

- Mellon metadata

- IdP metadata

- HTTP requests and responses

- HTTP headers

- SAML message content as decoded pretty XML

- Apache environment variables

- Session infomation

Although Mellon does log some `DEBUG` messages to the Apache error log that information is often incomplete and mixed in with other irrelevant messages. The SAML message content has to be gathered independently via other tools (Inspect SAML messages), configuring Apache to log all HTTP headers is obscure and verbose, there is no easy way to log all Apache environment variables associated with a request, and the SAML metadata and Mellon configuration is independent of the log data. Finally all these indpendent pieces of data gathered from multiple sources need to be correlated to produce a coherent sequence while at the same time removing a lot of extraneous irrelevant non-SAML data.

Apache logging also suffers from some serious limitations when trying to record SAML data. Apache enforces a hard limit on the length of a log message which often results in truncating SAML messages. Apache log messages are reformatted, newlines are removed and other charaters are escaped, this makes trying to read XML documents extremely difficult unless you post-process the log.

If you are a support person trying to help an administrator with their Mellon deployment is is very difficult to get a 3rd party whose is not familiar with the various operations to gather the necessary information in a cohesive form amenable for remote diagnostic review.

It would be really nice if Mellon could gather all this information in protocol sequence in a single file without other irrelvant Apache messages and without the need for any post-processing of the log data.

Mellon has been extended to gather all the above relevant information in a human readable format. The feature is called Mellon Diagnostics. The diagnostics feature is new as of July 2017 and it must be enabled at compile time thus your version of Mellon may not have it. Because the feature is new the format and content of the diagnostic data is expected to evolve.

#### 8.5.1. Using Mellon Diagnostics

Currently Mellon diagnostics supports these new Mellon directives. These directives are module level and as such should be declared outside of any location blocks in your Apache configuration.

MellonDiagnosticFile

  If Mellon was built with diagnostic capability then diagnostic is written here, it may be either a filename or a pipe. If it’s a filename then the resulting path is relative to the ServerRoot. If the value is preceeded by the pipe character "|" it should be followed by a path to a program to receive the log information on its standard input. Default: `logs/mellon_diagnostics`

MellonDiagnosticEnable

  If Mellon was built with diagnostic capability then this is a list of words controlling diagnostic output. Currently only `On` and `Off` are supported. Default: `Off`

To enable diagnostic logging add this line to your Apache configuration file where you keep your Mellon configuration.

    MellonDiagnosticEnable On

Restart Apache and perform some operation that involves Mellon. In your Apache log directory will be a file called `mellon_diagnostics` (or whatever `MellonDiagnosticFile` was set to).

| Diagnostic logging may potentially contain security sensitive information. Diagnostic logging is verbose and will generate large files. Therefore you should enable diagnostic logging only for the minimum duration necessary.

You may wish to review diagnostic output in Example Mellon Diagnostics captured when the demo authentication was executed.

## 9. Potential Problems

### 9.1. It’s the metadata

The vast majority of SAML deployment problems can be traced back to metadata.

- Is your metadata current?

- Have you loaded your most recent SP metadata? Did you restart Apache after modifying the SP metadata.

- Has your IdP loaded the exactly the same metadata Mellon is reading at Apache start-up.

- Have you loaded your most recent IdP metadata? Did you restart Apache after modifying the SP metadata.

- Did you make a change to your entityID?

- Did you make a change to the `MellonEndpointPath` without regenerating your SP metadata and loading the new metadata into both Mellon and your IdP? Remember the `MellonEndpointPath` establishes all the SAML endpoint URL’s that appear in your metadata. See Incorrect MellonEndpointPath and MellonEndpointPath

- Did you modify any of the keys or certs without both updating the mellon config and your SP metadata?

### 9.2. Behavior does not change after modifying any SAML file

Mellon reads it’s configuration at Apache start-up. If you make any change to any file Mellon reads you will not see those changes reflected until after you restart Apache.

### 9.3. Are the Mellon configuration directives syntactically correct?

Apache will not start if there is any error in any of the configuration files it reads. An easy way to test the correctness of your Apache configuration directives without starting the server and examining the error logs is to use the the `apachectl` command line tool with the `configtest` option, e.g.

    apachectl configtest

### 9.4. No AuthnRequest sent to IdP

During debugging you may discover the entire Web-SSO flow is not executed, the IdP is never contacted. This is because Mellon implements sessions. The session identifier is communicated in the cookie `mellon-cookie` (or whatever is the current value of the Mellon directive `MellonVariable`). If you had previously successfully authenticated against the IdP the browser will have been sent the Mellon session ID in it’s cookie. When Mellon gets a request to authenticate a resource it first checks to see if it has a valid session based on the identifier passed as the Mellon cookie. If there is a valid session Mellon will use that cached session information instead of contacting the IdP. Deleting the `mellon-cookie` from the browser will cause Mellon to believe there is no pre-existing session.

### 9.5. Incorrect MellonEndpointPath

1. <mellon_endpoint_path,`MellonEndpointPath`>>

     <Location />
        MellonEndpointPath /mellon/  (1)
     </Location>

1 | The definition of `MellonEndpointPath` in your Apache Mellon configuration must match the path component in each of your Service `Location` declarations in your SP metadata. See MellonEndpointPath for more detail.

    <SPSSODescriptor>
      <SingleLogoutService
        Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
        Location="https://mellon.example.com/mellon/logout" />  (1)
      <SingleLogoutService
        Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
        Location="https://mellon.example.com/mellon/logout" />  (1)
      <AssertionConsumerService
        index="0"
        isDefault="true"
        Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
        Location="https://mellon.example.com/mellon/postResponse" />  (1)
      <AssertionConsumerService
        index="1"
        Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact"
        Location="https://mellon.example.com/mellon/artifactResponse" />  (1)
      <AssertionConsumerService
        index="2"
        Binding="urn:oasis:names:tc:SAML:2.0:bindings:PAOS"
        Location="https://mellon.example.com/mellon/paosResponse" />  (1)
    </SPSSODescriptor>

1 | Each Service `Location` URL in your SP metadata must have a path component that starts with your `MellonEndpointPath` and appends exactly one directory component to it, that final directory component is one of the Mellon endpoints as described in Mellon Endpoints. Here the `MellonEndpointPath` is highlighted in the `Location` attributes of the metadata.

### 9.6. HTTP_BAD_REQUEST - Invalid Destination on Response

If after posting the Assertion to your `postResponse` endpoint you get a HTTP_BAD_REQUEST error with status code 400 and a page that says:

    Your browser sent a request that this server could not understand.

and in the Apache log file there is a Mellon message like this:

    Invalid Destination on Response. Should be: https://xxx/mellon/postResponse

Then you have failed one of the SAML security checks. There is a SAML requirement the recipient of a message verifies the intended destination of the message is the actual SAML endpoint it was received on. This is to prevent malicious forwarding of messages to unintended recipients.

To perform this check what Mellon does is build a URL by asking Apache what scheme, hostname and port it is running under and then appends the MellonEndpointPath and the Mellon endpoint to it. This becomes the URL the message was received on. Mellon then does a string comparison to see if this manufactured URL is identical to the `Destination` attribute in the SAML message. If they are not the same string the test fails and a HTTP_BAD_REQUEST is returned.

There are two potential causes for this failure:

1. Incorrect Apache `ServerName`. See the Apache ServerName discussion for more details. This problem usually occurs when Mellon is running behind a load balancer or SSL terminator.

2. Mismatch between the Mellon metadata and the `MellonEndpointPath` in your Mellon configuration. If the scheme, hostname and port are correct then the problem must be in path component of the URL. The SAML `Destination` attribute is read from the provider’s metadata. The `MellonEndpointPath` is read from Mellon’s configuration. The two must be in sync. Verify the location endpoints in Mellon’s metadata match the value of `MellonEndpointPath`. See the discussion of MellonEndpointPath for more details. The `Destination` check may also fail because one URL has an explicit port but the other does not, this can occur wit the standard HTTP port 80 and HTTPS port 443, see Standard Ports for more detail.

### 9.7. Mellon metadata out of sync with Mellon configuration

Mellon’s metadata and it’s Apache configuration directives have data elements in common but are maintained independently. The Apache configuration directives in common with the metadata are:

- `MellonSPentityId`

- `MellonSPPrivateKeyFile`

- `MellonSPCertFile`

- `MellonEndpointPath`

This can lead to problems if you:

- Generate metadata not consistent with these values in your Apache configuration directives.

- Edit the above Apache configuration directives without regenerating and reloading your metadata.

- Fail to load the current SP metadata by restarting Apache.

- Fail to load the current SP metadata into the IdP.

You may wish to review How is Mellon metadata created? and MellonEndpointPath.

### 9.8. Time Sync

SAML like many authentication protocols (i.e. Kerberos) rely on timestamps to validate messages. If you see one of these errors in the httpd logs:

    [auth_mellon:error] [pid xxx] [client xxx] NotBefore in Condition was in the future.
    [auth_mellon:error] [pid xxx] [client xxx] NotOnOrAfter in Condition was in the past.

Then it’s likely either the Mellon node or the IdP node are not time synchronized. You can check the status of your time sync with the `chronyc` command line tool, for example:

    $ chronyc sources
    210 Number of sources = 4
    MS Name/IP address         Stratum Poll Reach LastRx Last sample
    ===============================================================================
    ^? tock.no-such-agency.net       0  10     0   10y     +0ns[   +0ns] +/-    0ns
    ^? static-74-104-167-114.bst     0  10     0   10y     +0ns[   +0ns] +/-    0ns
    ^? 69.195.159.158                0  10     0   10y     +0ns[   +0ns] +/-    0ns
    ^? freemont.nerdboy.net.au       0  10     0   10y     +0ns[   +0ns] +/-    0ns

If the `Reach` column has zeros in it you are not synchronizing your clock. This may be due to a firewall blocking the NTP port. Trying opening your NTP port or using a different server in `/etc/chrony.conf`.

## 10. Glossary

entityID

  The unique name of a SAML provider. The entityID must be a URI. Often entityID’s are are URL’s however the choice of using a URL as an entityID does not have any meaning in SAML other than it is a convenient way to to have a unique URI. It is best to choose an entityID that will not change over time as SAML services inevitably migrate between hosts in a deployment. Once again, an entityID is a unique name for a SAML service, it is nothing more than that.

Assertion

  Data produced by a SAML authority (e.g. IdP) with respect to a specific subject. The assertion may convey authentication of the subject, attributes associated with the subject or authorization information for the subject in regards to a specific resource.

Identity Provider

  An identity provider is a SAML authority which provides authentication services proving the identity of a principal. The proof of identity is conveyed a SAML assertion along with additional information about the subject (attributes) which the service provider may choose to utilize when making authorization decisions.

IdP

  Acronym for Identity Provider

Profile

  A profile is a set of rules for one of several purposes; each set is given a name in the pattern “xxx profile of SAML” or “xxx SAML profile”.

  - Rules for how to embed assertions into and extract them from a protocol or other context of use.

  - Rules for using SAML protocol messages in a particular context of use.

  - Rules for mapping attributes expressed in SAML to another attribute representation system. Such a set of rules is known as an “attribute profile”.

SAML

  Security Assert Markup Language.

Service Provider

  A service provider is a SAML relying party which provides a service to a user who must be authenticated and authorized by the service in order to use the service. A web application is a common example.

SP

  Acronym for Service Provider.

## Appendix A: Appendix

### A.1. Example On-The-Wire AuthnRequest

This is is the "on the wire" HTTP data for the <AuthnRequest> Example using the HTTP Redirect Binding.

    GET https://rhsso.example.com:8443/auth/realms/test/protocol/saml?SAMLRequest=hZJBT8JAEIX%2FSrN32NKWAptCQkASEjQE1IMXs6lj2KS7W3emiv%2FeaRHFi5w2eTsvb76XKVDbqlbzhg5uB28NIEVHWzlU3cdUNMEpr9GgctoCKirVfn67UUk%2FVnXw5EtfiQvL%2Fw6NCIGMdyJaL6fieTgZJPkiTeP8JstHk1U%2BTOMkWcWLbDkfreJMRI8QkOengu1sQmxg7ZC0I5biwagX571kfD9IVTpRg%2BxJREtmME5T5zoQ1aikDAdE34ejtnUF%2FdJbNc6yVGrmlgF0ZVES%2B%2BQZSbYsIlp4h9BG%2FQdVnoZU2YTAb89whikNiWjlQwldt1PxqiuElmDLJZh3%2BFHm507asMZC2EN4NyU87Da%2F%2B1uoKu8uAb4lWXukHWDdLiFmRbu36moKs%2BtmC6RfNOlCXvqK01HcMel6ufUM89miWH2liFYxL73XblRR0A4NF8KIHPax4J6JsSk0IOTsFPn39GZf&RelayState=https%3A%2F%2Fmellon.example.com%2Fprivate%2Finfo.html&SigAlg=http%3A%2F%2Fwww.w3.org%2F2000%2F09%2Fxmldsig%23rsa-sha1&Signature=GJ%2BC%2BEwcPpOmAfYwMdMcAPSkX2y1Da634jrm1oWWs8Ozyb7P%2FumIk9HaNbfJZvaHc6HyOxYXhCpqb6NJrRm%2BrY1NSOJqjtt3kXldNLKecFfhKamzfOfAufKTPGGSZNAuwRTiQCkrLuFt8A%2BezEuCswNDADSRJGLL9aYX8A8G23IcLeVuqobtrCH9bSr2wgO0uy61o1s5bDlA6ceKwrjle%2F6TofFUWBYOB6pzRL40AzmNsvKieHqSOCxo6uNKQdEZQYomF9fi%2FuCPovIn5AdRFC1wcx%2BeGYi%2BDS6R4lbEnrhu8RfEmxhA8PJHDoTMH2fcfD0jyUh%2BejtLdqCUFJ9ppQ%3D%3D HTTP/1.1

### A.2. Example On-the-Wire <Assertion> response

This is is the "on the wire" HTTP data for the <Assertion> Example using the HTTP Post Binding.

    <HTML><HEAD><TITLE>SAML HTTP Post Binding</TITLE></HEAD><BODY Onload=\"document.forms[0].submit()\"><FORM METHOD=\"POST\" ACTION=\"https://mellon.example.com/mellon/postResponse\"><INPUT TYPE=\"HIDDEN\" NAME=\"SAMLResponse\" VALUE=\"[encoded data, 13488 characters]\"/><INPUT TYPE=\"HIDDEN\" NAME=\"RelayState\" VALUE=\"https://mellon.example.com/private/info.html\"/><NOSCRIPT><P>JavaScript is disabled. We strongly recommend to enable it. Click the button below to continue.</P><INPUT TYPE=\"SUBMIT\" VALUE=\"CONTINUE\" /></NOSCRIPT></FORM></BODY></HTML>

### A.3. Example Mellon Diagnostics

Here is the diagnostics output as described in Mellon Diagnostics for our authentication example.

    ---------------------------------- New Request ---------------------------------
    GET - /saml-test/protected.html
    log_id: (null)
    server: name=/etc/httpd/conf.d/ssl.conf, scheme=https hostname=mellon.example.com port=443
    pid: 21576, tid: 140251630954624
    unparsed_uri: /saml-test/protected.html
    uri: /saml-test/protected.html
    path_info:
    filename: /var/www/html/saml-test/protected.html
    query args: (null)
    Request Headers:
      Host: mellon.example.com
      Connection: keep-alive
      Cache-Control: max-age=0
      Upgrade-Insecure-Requests: 1
      User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36
      Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
      DNT: 1
      Accept-Encoding: gzip, deflate, br
      Accept-Language: en-US,en;q=0.8
      Cookie: mellon-cookie=aa8aefac8bc813f194b1a8d97e3a4058
    Mellon Directory Configuration for URL: /saml-test/protected.html
      MellonEnable (enable): auth
      MellonVariable (varname): cookie
      MellonSecureCookie (secure): Off
      MellonMergeEnvVars (merge_env_vars): (null)
      MellonEnvVarsIndexStart (env_vars_index_start): -1
      MellonEnvVarsSetCount (env_vars_count_in_n): On
      MellonCookieDomain (cookie_domain): (null)
      MellonCookiePath (cookie_path): (null)
      MellonCond (cond): 0 items
      MellonSetEnv (envattr): 0 items
      MellonUser (userattr): NAME_ID
      MellonIdP (idpattr): IDP
      MellonSessionDump (dump_session): Off
      MellonSamlResponseDump (dump_saml_response): Off
      MellonEndpointPath (endpoint_path): /mellon/
      MellonSPMetadataFile (sp_metadata_file):
        pathname: "/etc/httpd/saml2/demo_sp_metadata.xml"
          <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
          <EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
                            xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
                            xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
                            entityID="https://mellon.example.com/mellon/metadata">
           <SPSSODescriptor
             AuthnRequestsSigned="true"
             WantAssertionsSigned="true"
             protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
             <KeyDescriptor use="signing">
               <ds:KeyInfo>
                 <ds:X509Data>
                   <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
                 </ds:X509Data>
               </ds:KeyInfo>
             </KeyDescriptor>
             <KeyDescriptor use="encryption">
               <ds:KeyInfo>
                 <ds:X509Data>
                   <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
                 </ds:X509Data>
               </ds:KeyInfo>
             </KeyDescriptor>
             <SingleLogoutService
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
               Location="https://mellon.example.com/mellon/logout" />
             <SingleLogoutService
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
               Location="https://mellon.example.com/mellon/logout" />
             <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
             <AssertionConsumerService
               index="0"
               isDefault="true"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
               Location="https://mellon.example.com/mellon/postResponse" />
             <AssertionConsumerService
               index="1"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact"
               Location="https://mellon.example.com/mellon/artifactResponse" />
             <AssertionConsumerService
               index="2"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:PAOS"
               Location="https://mellon.example.com/mellon/paosResponse" />
           </SPSSODescriptor>
          </EntityDescriptor>
      MellonSPPrivateKeyFile (sp_private_key_file):
        pathname: "/etc/httpd/saml2/demo.key"
          -----BEGIN PRIVATE KEY-----
          MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQDHUXILDtuMxyFP
          6OW81hqfj9z+gC7sxR6U8bRPI4gFiNjkNF+4HMyrKtVtfwA5WJ1tJ4IaZbg4fGap
          iCcWQ5tjjuZ7CpZ6XLekq63OGrkgZxNm8L+AjvREv78iR4Myc4x6ybN1LwQnV+oD
          F0i9SAEPnfJCaCA+1+DC3RKy7+xtK3SVimUWwAHmkNU6N0wCVSNYn1KgnxBSCPTx
          2DifbyRl21SiokCfLSnktE++WBzRzldSxzMrkSfFoS7/uT232tbdw2NsJmHGLRGk
          myBrEC6BVhQ746NM1cLDtrOots7bNfZ3yfb3W1tpoKVOhM2se3OTKdidAQsaGlVu
          7QIhBqinAgMBAAECggEBAJtU662WfJ9vqJRgCnpp2QG02iM0vl0jGbw1ybFLHXxC
          s9TUxCv1tcNHdGEK8p++YaFpgskTsMfEmzVPuDZvpa+m9BO7op3ll/CrIp5W0SNh
          cQtuX6/OuKrDTC9oz+QHjNk8S7DtXS1UJDkYckWg0cLb8qqx/z86eh0isKnmtLg2
          H1+6L6mB9fcZldkcrU+kXT+dcDX85skMZAeBsrG4yaoX26AzVl8lEl2rJAQvpxj8
          5wGBC4riWY6TzMYiCjcS5JfZIlbhcZe61ej3A48NVBSKCP1XKo0xbKuOHIQuMeeW
          wSaboBwRzJ9JdTXlq5UWfLvmjXDc/HCwk/N7cj021uECgYEA5KkQr3cSKrMIkYoO
          H0Vnkw1kYYGUjtTL00Nfdkv7uGMF122nyt1ND0gpdS0jgNx3LSEam/gY35UWEjGH
          i8DGD04k8pvKDUsl8cuYPcC3oce1lLCGAnw+aHPC5wtA829CLOLtBfxXIhVAI0tp
          ECosD/A63/m1LC19XolOd10/PC8CgYEA3yZChEYZupDGJFZltiy0ZgUarvD2Ss4N
          QiRVR+CmpBrOKZdD8q6uUuqWQN9Rw7kXm8LxAPYwiIDVjxjYALF+j7/9Q1oZyKuv
          eHJdMe4eRUeqeaIKbxnFfKwGZ5rj97jwPrkUCxio75KZhpOcDHMSgBCBtzW0XIZl
          gTeQYOshZQkCgYB5TK6LRnEesabj/gaL1DejrMEJcMIsGvqdceocSSaZo/4fUA5o
          8YjFiJRlkrJ403ttN1h0UOJxCReSQzASlQr8Z4n2IWrILotMf6Kdb7R6YAUVgac1
          fk9k/bPw+OlVujmyshbmy/w1GmzRzFlJt/Vz5w50bnULoH4XPmOfspmvBQKBgBcJ
          rihVzGY0eCBcQxfxuZYmxMB25BaI+1luwtcu3EVo9wvYMA2n9xtcWLLN23UncMaF
          87ezswMEugeR+wrnSDezDISdkrfi8bSvqetzt/BTG8h+8DDUKk1avTaJCSwUDcmL
          9gPHQfmp2uvH5X5riudpzNqLUtmSjnwurlszKzlxAoGAR8STlDJhNph+p3cF8k25
          ydT1kypxnjzVG8CAV5/h3dUmc7j7gyV8NlWZfWacxMZWOBsrdVh0zhMNUPiLJaGd
          I1isOkmiN9JFYMMhHSnhPnTCIjmu6uBLxf8wotHAvzWOJPV7lUZbw21KIN3DS79F
          sGZ2QzGYn4inHG4UHClhZxU=
          -----END PRIVATE KEY-----
      MellonSPCertFile (sp_cert_file):
        pathname: "/etc/httpd/saml2/demo.cert"
          -----BEGIN CERTIFICATE-----
          MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=
          -----END CERTIFICATE-----
      MellonIdPPublicKeyFile (idp_public_key_file):
        file_data: NULL
      MellonIdPCAFile (idp_ca_file):
        file_data: NULL
      MellonIdPMetadataFile (idp_metadata): 1 items
      [ 0] Metadata
        pathname: "/etc/httpd/saml2/demo_keycloak_ipa_idp_metadata.xml"
          <?xml version="1.0" encoding="UTF-8"?>
          <!--
            ~ Copyright 2016 Red Hat, Inc. and/or its affiliates
            ~ and other contributors as indicated by the @author tags.
            ~
            ~ Licensed under the Apache License, Version 2.0 (the "License");
            ~ you may not use this file except in compliance with the License.
            ~ You may obtain a copy of the License at
            ~
            ~ http://www.apache.org/licenses/LICENSE-2.0
            ~
            ~ Unless required by applicable law or agreed to in writing, software
            ~ distributed under the License is distributed on an "AS IS" BASIS,
            ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
            ~ See the License for the specific language governing permissions and
            ~ limitations under the License.
            -->

          <EntitiesDescriptor Name="urn:keycloak" xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
          					xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
          	<EntityDescriptor entityID="https://rhsso.example.com:8443/auth/realms/ipa">
          		<IDPSSODescriptor WantAuthnRequestsSigned="true"
          			protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
                                  <KeyDescriptor use="signing">
                                    <dsig:KeyInfo>
                                      <dsig:KeyName>R2OGk9W0luNm_NtZbURWOrPlvFzSTDMimCVK5N1Mj5U</dsig:KeyName>
                                      <dsig:X509Data>
                                        <dsig:X509Certificate>MIIClTCCAX0CBgFeFdE9pDANBgkqhkiG9w0BAQsFADAOMQwwCgYDVQQDDANpcGEwHhcNMTcwODI0MTk1NDQ3WhcNMjcwODI0MTk1NjI3WjAOMQwwCgYDVQQDDANpcGEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgIPeag+JJmhtAkIGBwUT/req+jKC6c0Vl1Ngtzbcd07CP9mq1DomBkjuWl59J2urlEfrV4yT8avia0eYE6Dm/TqC74SHt3TVtiUliynAh/z2JvFlLb/EbGePSKrMnuNV8rV75YGcyE12vBRooUPx3hGaygsfaSOg+BijDuCSpbVdWSdVx9VecsWJfxSochOZUj6yvm/qTb8Ptl0x/o7/b/16GgjFRIKSFrdk8pVtMn1wCzpQQoGVHZmp1jrppGcp8KXIK54q7b4pPiTzlW6xhBgrmW2RtWQesCmN8ga1CVeBZKLsaH7argwGH5Ttz31iensqUO0degFu6nwCltgTVAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAFx8dl6RDle65q3IHIiGaL5fbJK5HxQiMXpk4N5riWQTP4g6xoTNAG4OFFUd4uRxt2ovdEdkbzhEy2lV4x626QdEfK5V9QKppupsTxTGA/4NMW9QCocAvFSpmYErmJIhfy6zzELoBK4Dpfcc3u1peHx2686msx6ExARF116d+5Xaps1dmPPy3yb2cCKzKbLhieqv+aLLrwz657ERUc4OnqEMEmmHFhHvPI7LRlS4AQ1/s1QlKcM9yqcu8WN3yKM/kuvZtZ0YTCSIl9W1b+I5v8wNoVFB22s7rfxs3DfJFaIImaTmRzaDX0MXgibEckrkigpO+anKe9B9z8CJdtlUHco=</dsig:X509Certificate>
                                      </dsig:X509Data>
                                    </dsig:KeyInfo>
                                  </KeyDescriptor>

          			<SingleLogoutService
          					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
          					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleLogoutService
          					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
          					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</NameIDFormat>
          			<SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleSignOnService
          				Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleSignOnService
          				Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          		</IDPSSODescriptor>
          	</EntityDescriptor>
          </EntitiesDescriptor>
      [ 0] Chain File
        file_data: NULL
      MellonIdPIgnore (idp_ignore):
      MellonSPentityId (sp_entity_id): (null)
      MellonOrganizationName (sp_org_name): 0 items
      MellonOrganizationDisplayName (sp_org_display_name): 0 items
      MellonOrganizationURL (sp_org_url): 0 items
      MellonSessionLength (session_length): -1
      MellonNoCookieErrorPage (no_cookie_error_page): (null)
      MellonNoSuccessErrorPage (no_success_error_page): (null)
      MellonDefaultLoginPath (login_path): /
      MellonDiscoveryURL (discovery_url): (null)
      MellonProbeDiscoveryTimeout (probe_discovery_timeout): -1
      MellonProbeDiscoveryIdP (probe_discovery_idp): 0 items
      MellonAuthnContextClassRef (authn_context_class_ref): 0 items
      MellonSubjectConfirmationDataAddressCheck (subject_confirmation_data_address_check): On
      MellonDoNotVerifyLogoutSignature (do_not_verify_logout_signature): 0 items
      MellonPostReplay (post_replay): On
      MellonECPSendIDPList (ecp_send_idplist): On
    enter function am_auth_mellon_user
    searching for session with key aa8aefac8bc813f194b1a8d97e3a4058 (session) ... not found
    am_auth_mellon_user am_enable_auth, no valid session
    [APLOG_DEBUG auth_mellon_util.c:2055] have_paos_media_type=False valid_paos_header=False is_paos=Falseenter function am_start_auth
    Loading SP Metadata
      pathname: "/etc/httpd/saml2/demo_sp_metadata.xml"
        <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
        <EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
                          xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
                          xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
                          entityID="https://mellon.example.com/mellon/metadata">
         <SPSSODescriptor
           AuthnRequestsSigned="true"
           WantAssertionsSigned="true"
           protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
           <KeyDescriptor use="signing">
             <ds:KeyInfo>
               <ds:X509Data>
                 <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
        BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
        NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
        hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
        tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
        rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
        ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
        T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
        s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
        HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
        LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
        AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
        g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
        cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
        Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
        XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
        YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
               </ds:X509Data>
             </ds:KeyInfo>
           </KeyDescriptor>
           <KeyDescriptor use="encryption">
             <ds:KeyInfo>
               <ds:X509Data>
                 <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
        BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
        NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
        hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
        tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
        rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
        ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
        T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
        s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
        HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
        LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
        AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
        g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
        cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
        Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
        XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
        YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
               </ds:X509Data>
             </ds:KeyInfo>
           </KeyDescriptor>
           <SingleLogoutService
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
             Location="https://mellon.example.com/mellon/logout" />
           <SingleLogoutService
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
             Location="https://mellon.example.com/mellon/logout" />
           <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
           <AssertionConsumerService
             index="0"
             isDefault="true"
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
             Location="https://mellon.example.com/mellon/postResponse" />
           <AssertionConsumerService
             index="1"
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact"
             Location="https://mellon.example.com/mellon/artifactResponse" />
           <AssertionConsumerService
             index="2"
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:PAOS"
             Location="https://mellon.example.com/mellon/paosResponse" />
         </SPSSODescriptor>
        </EntityDescriptor>
    Loading IdP Metadata
      pathname: "/etc/httpd/saml2/demo_keycloak_ipa_idp_metadata.xml"
        <?xml version="1.0" encoding="UTF-8"?>
        <!--
          ~ Copyright 2016 Red Hat, Inc. and/or its affiliates
          ~ and other contributors as indicated by the @author tags.
          ~
          ~ Licensed under the Apache License, Version 2.0 (the "License");
          ~ you may not use this file except in compliance with the License.
          ~ You may obtain a copy of the License at
          ~
          ~ http://www.apache.org/licenses/LICENSE-2.0
          ~
          ~ Unless required by applicable law or agreed to in writing, software
          ~ distributed under the License is distributed on an "AS IS" BASIS,
          ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
          ~ See the License for the specific language governing permissions and
          ~ limitations under the License.
          -->

        <EntitiesDescriptor Name="urn:keycloak" xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
        					xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
        	<EntityDescriptor entityID="https://rhsso.example.com:8443/auth/realms/ipa">
        		<IDPSSODescriptor WantAuthnRequestsSigned="true"
        			protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
                                <KeyDescriptor use="signing">
                                  <dsig:KeyInfo>
                                    <dsig:KeyName>R2OGk9W0luNm_NtZbURWOrPlvFzSTDMimCVK5N1Mj5U</dsig:KeyName>
                                    <dsig:X509Data>
                                      <dsig:X509Certificate>MIIClTCCAX0CBgFeFdE9pDANBgkqhkiG9w0BAQsFADAOMQwwCgYDVQQDDANpcGEwHhcNMTcwODI0MTk1NDQ3WhcNMjcwODI0MTk1NjI3WjAOMQwwCgYDVQQDDANpcGEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgIPeag+JJmhtAkIGBwUT/req+jKC6c0Vl1Ngtzbcd07CP9mq1DomBkjuWl59J2urlEfrV4yT8avia0eYE6Dm/TqC74SHt3TVtiUliynAh/z2JvFlLb/EbGePSKrMnuNV8rV75YGcyE12vBRooUPx3hGaygsfaSOg+BijDuCSpbVdWSdVx9VecsWJfxSochOZUj6yvm/qTb8Ptl0x/o7/b/16GgjFRIKSFrdk8pVtMn1wCzpQQoGVHZmp1jrppGcp8KXIK54q7b4pPiTzlW6xhBgrmW2RtWQesCmN8ga1CVeBZKLsaH7argwGH5Ttz31iensqUO0degFu6nwCltgTVAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAFx8dl6RDle65q3IHIiGaL5fbJK5HxQiMXpk4N5riWQTP4g6xoTNAG4OFFUd4uRxt2ovdEdkbzhEy2lV4x626QdEfK5V9QKppupsTxTGA/4NMW9QCocAvFSpmYErmJIhfy6zzELoBK4Dpfcc3u1peHx2686msx6ExARF116d+5Xaps1dmPPy3yb2cCKzKbLhieqv+aLLrwz657ERUc4OnqEMEmmHFhHvPI7LRlS4AQ1/s1QlKcM9yqcu8WN3yKM/kuvZtZ0YTCSIl9W1b+I5v8wNoVFB22s7rfxs3DfJFaIImaTmRzaDX0MXgibEckrkigpO+anKe9B9z8CJdtlUHco=</dsig:X509Certificate>
                                    </dsig:X509Data>
                                  </dsig:KeyInfo>
                                </KeyDescriptor>

        			<SingleLogoutService
        					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
        					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        			<SingleLogoutService
        					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
        					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</NameIDFormat>
        			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
        			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat>
        			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</NameIDFormat>
        			<SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
        				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        			<SingleSignOnService
        				Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
        				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        			<SingleSignOnService
        				Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
        				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        		</IDPSSODescriptor>
        	</EntityDescriptor>
        </EntitiesDescriptor>
    [APLOG_DEBUG auth_mellon_handler.c:3498] Redirecting to login URL: https://mellon.example.com/mellon/login?ReturnTo=https%3A%2F%2Fmellon.example.com%2Fsaml%2Dtest%2Fprotected.html&IdP=https%3A%2F%2Frhsso.example.com%3A8443%2Fauth%2Frealms%2Fipa
    === Response ===
    Status: 303 See Other(303)
    user: (null) auth_type=(null)
    Response Headers:
      Cache-Control: private, max-age=0, must-revalidate
      Location: https://mellon.example.com/mellon/login?ReturnTo=https%3A%2F%2Fmellon.example.com%2Fsaml%2Dtest%2Fprotected.html&IdP=https%3A%2F%2Frhsso.example.com%3A8443%2Fauth%2Frealms%2Fipa
      Content-Length: 388
      Keep-Alive: timeout=5, max=100
      Connection: Keep-Alive
      Content-Type: text/html; charset=iso-8859-1
    Response Error Headers:
    Environment:
      UNIQUE_ID: WabkjcTYa6iga7y800KGZQAAAAA
    ---------------------------------- New Request ---------------------------------
    GET - /mellon/login
    log_id: (null)
    server: name=/etc/httpd/conf.d/ssl.conf, scheme=https hostname=mellon.example.com port=443
    pid: 21576, tid: 140251630954624
    unparsed_uri: /mellon/login?ReturnTo=https%3A%2F%2Fmellon.example.com%2Fsaml%2Dtest%2Fprotected.html&IdP=https%3A%2F%2Frhsso.example.com%3A8443%2Fauth%2Frealms%2Fipa
    uri: /mellon/login
    path_info: /login
    filename: /var/www/html/mellon
    query args: ReturnTo=https%3A%2F%2Fmellon.example.com%2Fsaml%2Dtest%2Fprotected.html&IdP=https%3A%2F%2Frhsso.example.com%3A8443%2Fauth%2Frealms%2Fipa
    Request Headers:
      Host: mellon.example.com
      Connection: keep-alive
      Cache-Control: max-age=0
      Upgrade-Insecure-Requests: 1
      User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36
      Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
      DNT: 1
      Accept-Encoding: gzip, deflate, br
      Accept-Language: en-US,en;q=0.8
      Cookie: mellon-cookie=aa8aefac8bc813f194b1a8d97e3a4058
    Mellon Directory Configuration for URL: /mellon/login
      MellonEnable (enable): info
      MellonVariable (varname): cookie
      MellonSecureCookie (secure): Off
      MellonMergeEnvVars (merge_env_vars): (null)
      MellonEnvVarsIndexStart (env_vars_index_start): -1
      MellonEnvVarsSetCount (env_vars_count_in_n): On
      MellonCookieDomain (cookie_domain): (null)
      MellonCookiePath (cookie_path): (null)
      MellonCond (cond): 0 items
      MellonSetEnv (envattr): 0 items
      MellonUser (userattr): NAME_ID
      MellonIdP (idpattr): IDP
      MellonSessionDump (dump_session): Off
      MellonSamlResponseDump (dump_saml_response): Off
      MellonEndpointPath (endpoint_path): /mellon/
      MellonSPMetadataFile (sp_metadata_file):
        pathname: "/etc/httpd/saml2/demo_sp_metadata.xml"
          <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
          <EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
                            xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
                            xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
                            entityID="https://mellon.example.com/mellon/metadata">
           <SPSSODescriptor
             AuthnRequestsSigned="true"
             WantAssertionsSigned="true"
             protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
             <KeyDescriptor use="signing">
               <ds:KeyInfo>
                 <ds:X509Data>
                   <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
                 </ds:X509Data>
               </ds:KeyInfo>
             </KeyDescriptor>
             <KeyDescriptor use="encryption">
               <ds:KeyInfo>
                 <ds:X509Data>
                   <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
                 </ds:X509Data>
               </ds:KeyInfo>
             </KeyDescriptor>
             <SingleLogoutService
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
               Location="https://mellon.example.com/mellon/logout" />
             <SingleLogoutService
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
               Location="https://mellon.example.com/mellon/logout" />
             <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
             <AssertionConsumerService
               index="0"
               isDefault="true"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
               Location="https://mellon.example.com/mellon/postResponse" />
             <AssertionConsumerService
               index="1"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact"
               Location="https://mellon.example.com/mellon/artifactResponse" />
             <AssertionConsumerService
               index="2"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:PAOS"
               Location="https://mellon.example.com/mellon/paosResponse" />
           </SPSSODescriptor>
          </EntityDescriptor>
      MellonSPPrivateKeyFile (sp_private_key_file):
        pathname: "/etc/httpd/saml2/demo.key"
          -----BEGIN PRIVATE KEY-----
          MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQDHUXILDtuMxyFP
          6OW81hqfj9z+gC7sxR6U8bRPI4gFiNjkNF+4HMyrKtVtfwA5WJ1tJ4IaZbg4fGap
          iCcWQ5tjjuZ7CpZ6XLekq63OGrkgZxNm8L+AjvREv78iR4Myc4x6ybN1LwQnV+oD
          F0i9SAEPnfJCaCA+1+DC3RKy7+xtK3SVimUWwAHmkNU6N0wCVSNYn1KgnxBSCPTx
          2DifbyRl21SiokCfLSnktE++WBzRzldSxzMrkSfFoS7/uT232tbdw2NsJmHGLRGk
          myBrEC6BVhQ746NM1cLDtrOots7bNfZ3yfb3W1tpoKVOhM2se3OTKdidAQsaGlVu
          7QIhBqinAgMBAAECggEBAJtU662WfJ9vqJRgCnpp2QG02iM0vl0jGbw1ybFLHXxC
          s9TUxCv1tcNHdGEK8p++YaFpgskTsMfEmzVPuDZvpa+m9BO7op3ll/CrIp5W0SNh
          cQtuX6/OuKrDTC9oz+QHjNk8S7DtXS1UJDkYckWg0cLb8qqx/z86eh0isKnmtLg2
          H1+6L6mB9fcZldkcrU+kXT+dcDX85skMZAeBsrG4yaoX26AzVl8lEl2rJAQvpxj8
          5wGBC4riWY6TzMYiCjcS5JfZIlbhcZe61ej3A48NVBSKCP1XKo0xbKuOHIQuMeeW
          wSaboBwRzJ9JdTXlq5UWfLvmjXDc/HCwk/N7cj021uECgYEA5KkQr3cSKrMIkYoO
          H0Vnkw1kYYGUjtTL00Nfdkv7uGMF122nyt1ND0gpdS0jgNx3LSEam/gY35UWEjGH
          i8DGD04k8pvKDUsl8cuYPcC3oce1lLCGAnw+aHPC5wtA829CLOLtBfxXIhVAI0tp
          ECosD/A63/m1LC19XolOd10/PC8CgYEA3yZChEYZupDGJFZltiy0ZgUarvD2Ss4N
          QiRVR+CmpBrOKZdD8q6uUuqWQN9Rw7kXm8LxAPYwiIDVjxjYALF+j7/9Q1oZyKuv
          eHJdMe4eRUeqeaIKbxnFfKwGZ5rj97jwPrkUCxio75KZhpOcDHMSgBCBtzW0XIZl
          gTeQYOshZQkCgYB5TK6LRnEesabj/gaL1DejrMEJcMIsGvqdceocSSaZo/4fUA5o
          8YjFiJRlkrJ403ttN1h0UOJxCReSQzASlQr8Z4n2IWrILotMf6Kdb7R6YAUVgac1
          fk9k/bPw+OlVujmyshbmy/w1GmzRzFlJt/Vz5w50bnULoH4XPmOfspmvBQKBgBcJ
          rihVzGY0eCBcQxfxuZYmxMB25BaI+1luwtcu3EVo9wvYMA2n9xtcWLLN23UncMaF
          87ezswMEugeR+wrnSDezDISdkrfi8bSvqetzt/BTG8h+8DDUKk1avTaJCSwUDcmL
          9gPHQfmp2uvH5X5riudpzNqLUtmSjnwurlszKzlxAoGAR8STlDJhNph+p3cF8k25
          ydT1kypxnjzVG8CAV5/h3dUmc7j7gyV8NlWZfWacxMZWOBsrdVh0zhMNUPiLJaGd
          I1isOkmiN9JFYMMhHSnhPnTCIjmu6uBLxf8wotHAvzWOJPV7lUZbw21KIN3DS79F
          sGZ2QzGYn4inHG4UHClhZxU=
          -----END PRIVATE KEY-----
      MellonSPCertFile (sp_cert_file):
        pathname: "/etc/httpd/saml2/demo.cert"
          -----BEGIN CERTIFICATE-----
          MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=
          -----END CERTIFICATE-----
      MellonIdPPublicKeyFile (idp_public_key_file):
        file_data: NULL
      MellonIdPCAFile (idp_ca_file):
        file_data: NULL
      MellonIdPMetadataFile (idp_metadata): 1 items
      [ 0] Metadata
        pathname: "/etc/httpd/saml2/demo_keycloak_ipa_idp_metadata.xml"
          <?xml version="1.0" encoding="UTF-8"?>
          <!--
            ~ Copyright 2016 Red Hat, Inc. and/or its affiliates
            ~ and other contributors as indicated by the @author tags.
            ~
            ~ Licensed under the Apache License, Version 2.0 (the "License");
            ~ you may not use this file except in compliance with the License.
            ~ You may obtain a copy of the License at
            ~
            ~ http://www.apache.org/licenses/LICENSE-2.0
            ~
            ~ Unless required by applicable law or agreed to in writing, software
            ~ distributed under the License is distributed on an "AS IS" BASIS,
            ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
            ~ See the License for the specific language governing permissions and
            ~ limitations under the License.
            -->

          <EntitiesDescriptor Name="urn:keycloak" xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
          					xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
          	<EntityDescriptor entityID="https://rhsso.example.com:8443/auth/realms/ipa">
          		<IDPSSODescriptor WantAuthnRequestsSigned="true"
          			protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
                                  <KeyDescriptor use="signing">
                                    <dsig:KeyInfo>
                                      <dsig:KeyName>R2OGk9W0luNm_NtZbURWOrPlvFzSTDMimCVK5N1Mj5U</dsig:KeyName>
                                      <dsig:X509Data>
                                        <dsig:X509Certificate>MIIClTCCAX0CBgFeFdE9pDANBgkqhkiG9w0BAQsFADAOMQwwCgYDVQQDDANpcGEwHhcNMTcwODI0MTk1NDQ3WhcNMjcwODI0MTk1NjI3WjAOMQwwCgYDVQQDDANpcGEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgIPeag+JJmhtAkIGBwUT/req+jKC6c0Vl1Ngtzbcd07CP9mq1DomBkjuWl59J2urlEfrV4yT8avia0eYE6Dm/TqC74SHt3TVtiUliynAh/z2JvFlLb/EbGePSKrMnuNV8rV75YGcyE12vBRooUPx3hGaygsfaSOg+BijDuCSpbVdWSdVx9VecsWJfxSochOZUj6yvm/qTb8Ptl0x/o7/b/16GgjFRIKSFrdk8pVtMn1wCzpQQoGVHZmp1jrppGcp8KXIK54q7b4pPiTzlW6xhBgrmW2RtWQesCmN8ga1CVeBZKLsaH7argwGH5Ttz31iensqUO0degFu6nwCltgTVAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAFx8dl6RDle65q3IHIiGaL5fbJK5HxQiMXpk4N5riWQTP4g6xoTNAG4OFFUd4uRxt2ovdEdkbzhEy2lV4x626QdEfK5V9QKppupsTxTGA/4NMW9QCocAvFSpmYErmJIhfy6zzELoBK4Dpfcc3u1peHx2686msx6ExARF116d+5Xaps1dmPPy3yb2cCKzKbLhieqv+aLLrwz657ERUc4OnqEMEmmHFhHvPI7LRlS4AQ1/s1QlKcM9yqcu8WN3yKM/kuvZtZ0YTCSIl9W1b+I5v8wNoVFB22s7rfxs3DfJFaIImaTmRzaDX0MXgibEckrkigpO+anKe9B9z8CJdtlUHco=</dsig:X509Certificate>
                                      </dsig:X509Data>
                                    </dsig:KeyInfo>
                                  </KeyDescriptor>

          			<SingleLogoutService
          					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
          					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleLogoutService
          					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
          					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</NameIDFormat>
          			<SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleSignOnService
          				Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleSignOnService
          				Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          		</IDPSSODescriptor>
          	</EntityDescriptor>
          </EntitiesDescriptor>
      [ 0] Chain File
        file_data: NULL
      MellonIdPIgnore (idp_ignore):
      MellonSPentityId (sp_entity_id): (null)
      MellonOrganizationName (sp_org_name): 0 items
      MellonOrganizationDisplayName (sp_org_display_name): 0 items
      MellonOrganizationURL (sp_org_url): 0 items
      MellonSessionLength (session_length): -1
      MellonNoCookieErrorPage (no_cookie_error_page): (null)
      MellonNoSuccessErrorPage (no_success_error_page): (null)
      MellonDefaultLoginPath (login_path): /
      MellonDiscoveryURL (discovery_url): (null)
      MellonProbeDiscoveryTimeout (probe_discovery_timeout): -1
      MellonProbeDiscoveryIdP (probe_discovery_idp): 0 items
      MellonAuthnContextClassRef (authn_context_class_ref): 0 items
      MellonSubjectConfirmationDataAddressCheck (subject_confirmation_data_address_check): On
      MellonDoNotVerifyLogoutSignature (do_not_verify_logout_signature): 0 items
      MellonPostReplay (post_replay): On
      MellonECPSendIDPList (ecp_send_idplist): On
    enter function am_auth_mellon_user
    enter function am_handle_login
    Loading SP Metadata
      pathname: "/etc/httpd/saml2/demo_sp_metadata.xml"
        <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
        <EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
                          xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
                          xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
                          entityID="https://mellon.example.com/mellon/metadata">
         <SPSSODescriptor
           AuthnRequestsSigned="true"
           WantAssertionsSigned="true"
           protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
           <KeyDescriptor use="signing">
             <ds:KeyInfo>
               <ds:X509Data>
                 <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
        BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
        NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
        hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
        tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
        rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
        ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
        T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
        s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
        HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
        LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
        AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
        g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
        cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
        Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
        XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
        YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
               </ds:X509Data>
             </ds:KeyInfo>
           </KeyDescriptor>
           <KeyDescriptor use="encryption">
             <ds:KeyInfo>
               <ds:X509Data>
                 <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
        BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
        NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
        hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
        tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
        rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
        ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
        T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
        s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
        HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
        LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
        AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
        g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
        cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
        Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
        XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
        YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
               </ds:X509Data>
             </ds:KeyInfo>
           </KeyDescriptor>
           <SingleLogoutService
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
             Location="https://mellon.example.com/mellon/logout" />
           <SingleLogoutService
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
             Location="https://mellon.example.com/mellon/logout" />
           <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
           <AssertionConsumerService
             index="0"
             isDefault="true"
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
             Location="https://mellon.example.com/mellon/postResponse" />
           <AssertionConsumerService
             index="1"
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact"
             Location="https://mellon.example.com/mellon/artifactResponse" />
           <AssertionConsumerService
             index="2"
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:PAOS"
             Location="https://mellon.example.com/mellon/paosResponse" />
         </SPSSODescriptor>
        </EntityDescriptor>
    Loading IdP Metadata
      pathname: "/etc/httpd/saml2/demo_keycloak_ipa_idp_metadata.xml"
        <?xml version="1.0" encoding="UTF-8"?>
        <!--
          ~ Copyright 2016 Red Hat, Inc. and/or its affiliates
          ~ and other contributors as indicated by the @author tags.
          ~
          ~ Licensed under the Apache License, Version 2.0 (the "License");
          ~ you may not use this file except in compliance with the License.
          ~ You may obtain a copy of the License at
          ~
          ~ http://www.apache.org/licenses/LICENSE-2.0
          ~
          ~ Unless required by applicable law or agreed to in writing, software
          ~ distributed under the License is distributed on an "AS IS" BASIS,
          ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
          ~ See the License for the specific language governing permissions and
          ~ limitations under the License.
          -->

        <EntitiesDescriptor Name="urn:keycloak" xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
        					xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
        	<EntityDescriptor entityID="https://rhsso.example.com:8443/auth/realms/ipa">
        		<IDPSSODescriptor WantAuthnRequestsSigned="true"
        			protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
                                <KeyDescriptor use="signing">
                                  <dsig:KeyInfo>
                                    <dsig:KeyName>R2OGk9W0luNm_NtZbURWOrPlvFzSTDMimCVK5N1Mj5U</dsig:KeyName>
                                    <dsig:X509Data>
                                      <dsig:X509Certificate>MIIClTCCAX0CBgFeFdE9pDANBgkqhkiG9w0BAQsFADAOMQwwCgYDVQQDDANpcGEwHhcNMTcwODI0MTk1NDQ3WhcNMjcwODI0MTk1NjI3WjAOMQwwCgYDVQQDDANpcGEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgIPeag+JJmhtAkIGBwUT/req+jKC6c0Vl1Ngtzbcd07CP9mq1DomBkjuWl59J2urlEfrV4yT8avia0eYE6Dm/TqC74SHt3TVtiUliynAh/z2JvFlLb/EbGePSKrMnuNV8rV75YGcyE12vBRooUPx3hGaygsfaSOg+BijDuCSpbVdWSdVx9VecsWJfxSochOZUj6yvm/qTb8Ptl0x/o7/b/16GgjFRIKSFrdk8pVtMn1wCzpQQoGVHZmp1jrppGcp8KXIK54q7b4pPiTzlW6xhBgrmW2RtWQesCmN8ga1CVeBZKLsaH7argwGH5Ttz31iensqUO0degFu6nwCltgTVAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAFx8dl6RDle65q3IHIiGaL5fbJK5HxQiMXpk4N5riWQTP4g6xoTNAG4OFFUd4uRxt2ovdEdkbzhEy2lV4x626QdEfK5V9QKppupsTxTGA/4NMW9QCocAvFSpmYErmJIhfy6zzELoBK4Dpfcc3u1peHx2686msx6ExARF116d+5Xaps1dmPPy3yb2cCKzKbLhieqv+aLLrwz657ERUc4OnqEMEmmHFhHvPI7LRlS4AQ1/s1QlKcM9yqcu8WN3yKM/kuvZtZ0YTCSIl9W1b+I5v8wNoVFB22s7rfxs3DfJFaIImaTmRzaDX0MXgibEckrkigpO+anKe9B9z8CJdtlUHco=</dsig:X509Certificate>
                                    </dsig:X509Data>
                                  </dsig:KeyInfo>
                                </KeyDescriptor>

        			<SingleLogoutService
        					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
        					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        			<SingleLogoutService
        					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
        					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</NameIDFormat>
        			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
        			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat>
        			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</NameIDFormat>
        			<SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
        				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        			<SingleSignOnService
        				Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
        				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        			<SingleSignOnService
        				Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
        				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        		</IDPSSODescriptor>
        	</EntityDescriptor>
        </EntitiesDescriptor>
    SAML AuthnRequest: http_method=LASSO_HTTP_METHOD_REDIRECT
      <samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" ID="_A65FF17C0924D19BE0FEC241B49EA45C" Version="2.0" IssueInstant="2017-08-30T16:15:09Z" Destination="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" Consent="urn:oasis:names:tc:SAML:2.0:consent:current-implicit" SignType="0" SignMethod="0" ForceAuthn="false" IsPassive="false" AssertionConsumerServiceURL="https://mellon.example.com/mellon/postResponse">
        <saml:Issuer>https://mellon.example.com/mellon/metadata</saml:Issuer>
        <samlp:NameIDPolicy Format="urn:oasis:names:tc:SAML:2.0:nameid-format:transient" AllowCreate="true"/>
      </samlp:AuthnRequest>

    === Response ===
    Status: 303 See Other(303)
    user: (null) auth_type=(null)
    Response Headers:
      Cache-Control: private, max-age=0, must-revalidate
      Set-Cookie: mellon-cookie=cookietest; Version=1; Path=/; Domain=mellon.example.com;
      Location: https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml?SAMLRequest=hZLNbsIwEIRfJfIdnED4syBSSEBCohWCtodeKisswlJsp94NpW9fJ5SWXsrJ0nhHs99opyh1WYm0pqPZwnsNSMFZlwZF%2BzFjtTPCSlQojNSAggqxSx%2FWotcNReUs2cKW7Mbyv0MigiNlDQtW%2BYy9pcPBchmNsnDSi%2FNoMl%2BEy0XWi6N5PFmk8SBjwQs49PMz5u3ehFjDyiBJQ14Ko1EnHHf64VM0FNFAhJNXFuSeQRlJretIVKHg3B0RbRfOUlcldAurxTiO%2B1x6bu5Alhq5qiS%2FEvEGhQWZNQhN0n9MxWVIFLVz%2Fu0oH6EKRSxYWldAW%2B2MHWSJ0ABsfAfqBD9Keq2kCas1uB24kyrgebv%2BXV9DWVpzu%2F%2B3xCuLtAWsmiVYMm32Fm1LLrlv1kByL0lO%2Ba1vermJR0%2B6yjfWw3w2KFreKaJR1L5zaEcFOWlQ%2BUI8og%2F7yHzN5LHJ1cB4con8e3nJFw%3D%3D&RelayState=https%3A%2F%2Fmellon.example.com%2Fsaml-test%2Fprotected.html&SigAlg=http%3A%2F%2Fwww.w3.org%2F2000%2F09%2Fxmldsig%23rsa-sha1&Signature=gBd8iP4CvbWajeMQHKOMgc5NBx7i6Kf5gXcbSa54oehMXgpPJJuwlY8BLTH861vGnl7AxaO%2F2soJPai4D96aNowm8hr9FBokjvI%2FjwdEVtRiFlng18DpEXPTE1SAa4cuxWcLE3BAZD2HZ0sW%2F91sRGnymFH9lC4cDiU1pG9OBBI1pBYxjtrAM%2FHvEjDNZ0xYTwji8S6ltrM0bBFbTdftcn5YCwI31SAFVhopbPRTfiEhanTYChbjy7h%2Fp6BHTwfvcLw4Pud98phEIhXTdK4XIJGSN%2BmCYeXHQZPyGnRGZcmfmPrEcIpptT4a5xRkltfJPHUSLnI%2Ft9QsEuYm02%2F4%2BQ%3D%3D
      Content-Length: 1318
      Keep-Alive: timeout=5, max=99
      Connection: Keep-Alive
      Content-Type: text/html; charset=iso-8859-1
    Response Error Headers:
    Environment:
      UNIQUE_ID: WabkjcTYa6iga7y800KGZgAAAAA
      HTTPS: on
      SSL_TLS_SNI: mellon.example.com
    ---------------------------------- New Request ---------------------------------
    POST - /mellon/postResponse
    log_id: (null)
    server: name=/etc/httpd/conf.d/ssl.conf, scheme=https hostname=mellon.example.com port=443
    pid: 21593, tid: 140251630954624
    unparsed_uri: /mellon/postResponse
    uri: /mellon/postResponse
    path_info: /postResponse
    filename: /var/www/html/mellon
    query args: (null)
    Request Headers:
      Host: mellon.example.com
      Connection: keep-alive
      Content-Length: 15654
      Cache-Control: max-age=0
      Origin: https://rhsso.example.com:8443
      Upgrade-Insecure-Requests: 1
      User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36
      Content-Type: application/x-www-form-urlencoded
      Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
      DNT: 1
      Referer: https://rhsso.example.com:8443/auth/realms/ipa/login-actions/authenticate?code=qv8kqt2kFiT0YBmG8TIzcNzgxfFp6q_N15M5pS931Eo.caa7c606-3404-4961-8af9-ba27345d1f7b&execution=10aa0b63-d5d9-4960-8ad8-16720df6fc8e
      Accept-Encoding: gzip, deflate, br
      Accept-Language: en-US,en;q=0.8
      Cookie: mellon-cookie=cookietest
    Mellon Directory Configuration for URL: /mellon/postResponse
      MellonEnable (enable): info
      MellonVariable (varname): cookie
      MellonSecureCookie (secure): Off
      MellonMergeEnvVars (merge_env_vars): (null)
      MellonEnvVarsIndexStart (env_vars_index_start): -1
      MellonEnvVarsSetCount (env_vars_count_in_n): On
      MellonCookieDomain (cookie_domain): (null)
      MellonCookiePath (cookie_path): (null)
      MellonCond (cond): 0 items
      MellonSetEnv (envattr): 0 items
      MellonUser (userattr): NAME_ID
      MellonIdP (idpattr): IDP
      MellonSessionDump (dump_session): Off
      MellonSamlResponseDump (dump_saml_response): Off
      MellonEndpointPath (endpoint_path): /mellon/
      MellonSPMetadataFile (sp_metadata_file):
        pathname: "/etc/httpd/saml2/demo_sp_metadata.xml"
          <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
          <EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
                            xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
                            xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
                            entityID="https://mellon.example.com/mellon/metadata">
           <SPSSODescriptor
             AuthnRequestsSigned="true"
             WantAssertionsSigned="true"
             protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
             <KeyDescriptor use="signing">
               <ds:KeyInfo>
                 <ds:X509Data>
                   <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
                 </ds:X509Data>
               </ds:KeyInfo>
             </KeyDescriptor>
             <KeyDescriptor use="encryption">
               <ds:KeyInfo>
                 <ds:X509Data>
                   <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
                 </ds:X509Data>
               </ds:KeyInfo>
             </KeyDescriptor>
             <SingleLogoutService
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
               Location="https://mellon.example.com/mellon/logout" />
             <SingleLogoutService
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
               Location="https://mellon.example.com/mellon/logout" />
             <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
             <AssertionConsumerService
               index="0"
               isDefault="true"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
               Location="https://mellon.example.com/mellon/postResponse" />
             <AssertionConsumerService
               index="1"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact"
               Location="https://mellon.example.com/mellon/artifactResponse" />
             <AssertionConsumerService
               index="2"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:PAOS"
               Location="https://mellon.example.com/mellon/paosResponse" />
           </SPSSODescriptor>
          </EntityDescriptor>
      MellonSPPrivateKeyFile (sp_private_key_file):
        pathname: "/etc/httpd/saml2/demo.key"
          -----BEGIN PRIVATE KEY-----
          MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQDHUXILDtuMxyFP
          6OW81hqfj9z+gC7sxR6U8bRPI4gFiNjkNF+4HMyrKtVtfwA5WJ1tJ4IaZbg4fGap
          iCcWQ5tjjuZ7CpZ6XLekq63OGrkgZxNm8L+AjvREv78iR4Myc4x6ybN1LwQnV+oD
          F0i9SAEPnfJCaCA+1+DC3RKy7+xtK3SVimUWwAHmkNU6N0wCVSNYn1KgnxBSCPTx
          2DifbyRl21SiokCfLSnktE++WBzRzldSxzMrkSfFoS7/uT232tbdw2NsJmHGLRGk
          myBrEC6BVhQ746NM1cLDtrOots7bNfZ3yfb3W1tpoKVOhM2se3OTKdidAQsaGlVu
          7QIhBqinAgMBAAECggEBAJtU662WfJ9vqJRgCnpp2QG02iM0vl0jGbw1ybFLHXxC
          s9TUxCv1tcNHdGEK8p++YaFpgskTsMfEmzVPuDZvpa+m9BO7op3ll/CrIp5W0SNh
          cQtuX6/OuKrDTC9oz+QHjNk8S7DtXS1UJDkYckWg0cLb8qqx/z86eh0isKnmtLg2
          H1+6L6mB9fcZldkcrU+kXT+dcDX85skMZAeBsrG4yaoX26AzVl8lEl2rJAQvpxj8
          5wGBC4riWY6TzMYiCjcS5JfZIlbhcZe61ej3A48NVBSKCP1XKo0xbKuOHIQuMeeW
          wSaboBwRzJ9JdTXlq5UWfLvmjXDc/HCwk/N7cj021uECgYEA5KkQr3cSKrMIkYoO
          H0Vnkw1kYYGUjtTL00Nfdkv7uGMF122nyt1ND0gpdS0jgNx3LSEam/gY35UWEjGH
          i8DGD04k8pvKDUsl8cuYPcC3oce1lLCGAnw+aHPC5wtA829CLOLtBfxXIhVAI0tp
          ECosD/A63/m1LC19XolOd10/PC8CgYEA3yZChEYZupDGJFZltiy0ZgUarvD2Ss4N
          QiRVR+CmpBrOKZdD8q6uUuqWQN9Rw7kXm8LxAPYwiIDVjxjYALF+j7/9Q1oZyKuv
          eHJdMe4eRUeqeaIKbxnFfKwGZ5rj97jwPrkUCxio75KZhpOcDHMSgBCBtzW0XIZl
          gTeQYOshZQkCgYB5TK6LRnEesabj/gaL1DejrMEJcMIsGvqdceocSSaZo/4fUA5o
          8YjFiJRlkrJ403ttN1h0UOJxCReSQzASlQr8Z4n2IWrILotMf6Kdb7R6YAUVgac1
          fk9k/bPw+OlVujmyshbmy/w1GmzRzFlJt/Vz5w50bnULoH4XPmOfspmvBQKBgBcJ
          rihVzGY0eCBcQxfxuZYmxMB25BaI+1luwtcu3EVo9wvYMA2n9xtcWLLN23UncMaF
          87ezswMEugeR+wrnSDezDISdkrfi8bSvqetzt/BTG8h+8DDUKk1avTaJCSwUDcmL
          9gPHQfmp2uvH5X5riudpzNqLUtmSjnwurlszKzlxAoGAR8STlDJhNph+p3cF8k25
          ydT1kypxnjzVG8CAV5/h3dUmc7j7gyV8NlWZfWacxMZWOBsrdVh0zhMNUPiLJaGd
          I1isOkmiN9JFYMMhHSnhPnTCIjmu6uBLxf8wotHAvzWOJPV7lUZbw21KIN3DS79F
          sGZ2QzGYn4inHG4UHClhZxU=
          -----END PRIVATE KEY-----
      MellonSPCertFile (sp_cert_file):
        pathname: "/etc/httpd/saml2/demo.cert"
          -----BEGIN CERTIFICATE-----
          MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=
          -----END CERTIFICATE-----
      MellonIdPPublicKeyFile (idp_public_key_file):
        file_data: NULL
      MellonIdPCAFile (idp_ca_file):
        file_data: NULL
      MellonIdPMetadataFile (idp_metadata): 1 items
      [ 0] Metadata
        pathname: "/etc/httpd/saml2/demo_keycloak_ipa_idp_metadata.xml"
          <?xml version="1.0" encoding="UTF-8"?>
          <!--
            ~ Copyright 2016 Red Hat, Inc. and/or its affiliates
            ~ and other contributors as indicated by the @author tags.
            ~
            ~ Licensed under the Apache License, Version 2.0 (the "License");
            ~ you may not use this file except in compliance with the License.
            ~ You may obtain a copy of the License at
            ~
            ~ http://www.apache.org/licenses/LICENSE-2.0
            ~
            ~ Unless required by applicable law or agreed to in writing, software
            ~ distributed under the License is distributed on an "AS IS" BASIS,
            ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
            ~ See the License for the specific language governing permissions and
            ~ limitations under the License.
            -->

          <EntitiesDescriptor Name="urn:keycloak" xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
          					xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
          	<EntityDescriptor entityID="https://rhsso.example.com:8443/auth/realms/ipa">
          		<IDPSSODescriptor WantAuthnRequestsSigned="true"
          			protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
                                  <KeyDescriptor use="signing">
                                    <dsig:KeyInfo>
                                      <dsig:KeyName>R2OGk9W0luNm_NtZbURWOrPlvFzSTDMimCVK5N1Mj5U</dsig:KeyName>
                                      <dsig:X509Data>
                                        <dsig:X509Certificate>MIIClTCCAX0CBgFeFdE9pDANBgkqhkiG9w0BAQsFADAOMQwwCgYDVQQDDANpcGEwHhcNMTcwODI0MTk1NDQ3WhcNMjcwODI0MTk1NjI3WjAOMQwwCgYDVQQDDANpcGEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgIPeag+JJmhtAkIGBwUT/req+jKC6c0Vl1Ngtzbcd07CP9mq1DomBkjuWl59J2urlEfrV4yT8avia0eYE6Dm/TqC74SHt3TVtiUliynAh/z2JvFlLb/EbGePSKrMnuNV8rV75YGcyE12vBRooUPx3hGaygsfaSOg+BijDuCSpbVdWSdVx9VecsWJfxSochOZUj6yvm/qTb8Ptl0x/o7/b/16GgjFRIKSFrdk8pVtMn1wCzpQQoGVHZmp1jrppGcp8KXIK54q7b4pPiTzlW6xhBgrmW2RtWQesCmN8ga1CVeBZKLsaH7argwGH5Ttz31iensqUO0degFu6nwCltgTVAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAFx8dl6RDle65q3IHIiGaL5fbJK5HxQiMXpk4N5riWQTP4g6xoTNAG4OFFUd4uRxt2ovdEdkbzhEy2lV4x626QdEfK5V9QKppupsTxTGA/4NMW9QCocAvFSpmYErmJIhfy6zzELoBK4Dpfcc3u1peHx2686msx6ExARF116d+5Xaps1dmPPy3yb2cCKzKbLhieqv+aLLrwz657ERUc4OnqEMEmmHFhHvPI7LRlS4AQ1/s1QlKcM9yqcu8WN3yKM/kuvZtZ0YTCSIl9W1b+I5v8wNoVFB22s7rfxs3DfJFaIImaTmRzaDX0MXgibEckrkigpO+anKe9B9z8CJdtlUHco=</dsig:X509Certificate>
                                      </dsig:X509Data>
                                    </dsig:KeyInfo>
                                  </KeyDescriptor>

          			<SingleLogoutService
          					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
          					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleLogoutService
          					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
          					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</NameIDFormat>
          			<SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleSignOnService
          				Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleSignOnService
          				Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          		</IDPSSODescriptor>
          	</EntityDescriptor>
          </EntitiesDescriptor>
      [ 0] Chain File
        file_data: NULL
      MellonIdPIgnore (idp_ignore):
      MellonSPentityId (sp_entity_id): (null)
      MellonOrganizationName (sp_org_name): 0 items
      MellonOrganizationDisplayName (sp_org_display_name): 0 items
      MellonOrganizationURL (sp_org_url): 0 items
      MellonSessionLength (session_length): -1
      MellonNoCookieErrorPage (no_cookie_error_page): (null)
      MellonNoSuccessErrorPage (no_success_error_page): (null)
      MellonDefaultLoginPath (login_path): /
      MellonDiscoveryURL (discovery_url): (null)
      MellonProbeDiscoveryTimeout (probe_discovery_timeout): -1
      MellonProbeDiscoveryIdP (probe_discovery_idp): 0 items
      MellonAuthnContextClassRef (authn_context_class_ref): 0 items
      MellonSubjectConfirmationDataAddressCheck (subject_confirmation_data_address_check): On
      MellonDoNotVerifyLogoutSignature (do_not_verify_logout_signature): 0 items
      MellonPostReplay (post_replay): On
      MellonECPSendIDPList (ecp_send_idplist): On
    enter function am_auth_mellon_user
    enter function am_handle_post_reply
    Loading SP Metadata
      pathname: "/etc/httpd/saml2/demo_sp_metadata.xml"
        <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
        <EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
                          xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
                          xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
                          entityID="https://mellon.example.com/mellon/metadata">
         <SPSSODescriptor
           AuthnRequestsSigned="true"
           WantAssertionsSigned="true"
           protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
           <KeyDescriptor use="signing">
             <ds:KeyInfo>
               <ds:X509Data>
                 <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
        BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
        NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
        hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
        tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
        rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
        ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
        T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
        s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
        HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
        LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
        AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
        g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
        cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
        Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
        XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
        YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
               </ds:X509Data>
             </ds:KeyInfo>
           </KeyDescriptor>
           <KeyDescriptor use="encryption">
             <ds:KeyInfo>
               <ds:X509Data>
                 <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
        BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
        NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
        hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
        tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
        rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
        ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
        T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
        s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
        HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
        LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
        AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
        g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
        cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
        Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
        XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
        YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
               </ds:X509Data>
             </ds:KeyInfo>
           </KeyDescriptor>
           <SingleLogoutService
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
             Location="https://mellon.example.com/mellon/logout" />
           <SingleLogoutService
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
             Location="https://mellon.example.com/mellon/logout" />
           <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
           <AssertionConsumerService
             index="0"
             isDefault="true"
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
             Location="https://mellon.example.com/mellon/postResponse" />
           <AssertionConsumerService
             index="1"
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact"
             Location="https://mellon.example.com/mellon/artifactResponse" />
           <AssertionConsumerService
             index="2"
             Binding="urn:oasis:names:tc:SAML:2.0:bindings:PAOS"
             Location="https://mellon.example.com/mellon/paosResponse" />
         </SPSSODescriptor>
        </EntityDescriptor>
    Loading IdP Metadata
      pathname: "/etc/httpd/saml2/demo_keycloak_ipa_idp_metadata.xml"
        <?xml version="1.0" encoding="UTF-8"?>
        <!--
          ~ Copyright 2016 Red Hat, Inc. and/or its affiliates
          ~ and other contributors as indicated by the @author tags.
          ~
          ~ Licensed under the Apache License, Version 2.0 (the "License");
          ~ you may not use this file except in compliance with the License.
          ~ You may obtain a copy of the License at
          ~
          ~ http://www.apache.org/licenses/LICENSE-2.0
          ~
          ~ Unless required by applicable law or agreed to in writing, software
          ~ distributed under the License is distributed on an "AS IS" BASIS,
          ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
          ~ See the License for the specific language governing permissions and
          ~ limitations under the License.
          -->

        <EntitiesDescriptor Name="urn:keycloak" xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
        					xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
        	<EntityDescriptor entityID="https://rhsso.example.com:8443/auth/realms/ipa">
        		<IDPSSODescriptor WantAuthnRequestsSigned="true"
        			protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
                                <KeyDescriptor use="signing">
                                  <dsig:KeyInfo>
                                    <dsig:KeyName>R2OGk9W0luNm_NtZbURWOrPlvFzSTDMimCVK5N1Mj5U</dsig:KeyName>
                                    <dsig:X509Data>
                                      <dsig:X509Certificate>MIIClTCCAX0CBgFeFdE9pDANBgkqhkiG9w0BAQsFADAOMQwwCgYDVQQDDANpcGEwHhcNMTcwODI0MTk1NDQ3WhcNMjcwODI0MTk1NjI3WjAOMQwwCgYDVQQDDANpcGEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgIPeag+JJmhtAkIGBwUT/req+jKC6c0Vl1Ngtzbcd07CP9mq1DomBkjuWl59J2urlEfrV4yT8avia0eYE6Dm/TqC74SHt3TVtiUliynAh/z2JvFlLb/EbGePSKrMnuNV8rV75YGcyE12vBRooUPx3hGaygsfaSOg+BijDuCSpbVdWSdVx9VecsWJfxSochOZUj6yvm/qTb8Ptl0x/o7/b/16GgjFRIKSFrdk8pVtMn1wCzpQQoGVHZmp1jrppGcp8KXIK54q7b4pPiTzlW6xhBgrmW2RtWQesCmN8ga1CVeBZKLsaH7argwGH5Ttz31iensqUO0degFu6nwCltgTVAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAFx8dl6RDle65q3IHIiGaL5fbJK5HxQiMXpk4N5riWQTP4g6xoTNAG4OFFUd4uRxt2ovdEdkbzhEy2lV4x626QdEfK5V9QKppupsTxTGA/4NMW9QCocAvFSpmYErmJIhfy6zzELoBK4Dpfcc3u1peHx2686msx6ExARF116d+5Xaps1dmPPy3yb2cCKzKbLhieqv+aLLrwz657ERUc4OnqEMEmmHFhHvPI7LRlS4AQ1/s1QlKcM9yqcu8WN3yKM/kuvZtZ0YTCSIl9W1b+I5v8wNoVFB22s7rfxs3DfJFaIImaTmRzaDX0MXgibEckrkigpO+anKe9B9z8CJdtlUHco=</dsig:X509Certificate>
                                    </dsig:X509Data>
                                  </dsig:KeyInfo>
                                </KeyDescriptor>

        			<SingleLogoutService
        					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
        					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        			<SingleLogoutService
        					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
        					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</NameIDFormat>
        			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
        			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat>
        			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</NameIDFormat>
        			<SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
        				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        			<SingleSignOnService
        				Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
        				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        			<SingleSignOnService
        				Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
        				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
        		</IDPSSODescriptor>
        	</EntityDescriptor>
        </EntitiesDescriptor>
    SAMLResponse:
      <samlp:Response xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" ID="ID_cd361c13-dc8b-48b6-bc26-4982b07bf772" InResponseTo="_A65FF17C0924D19BE0FEC241B49EA45C" Version="2.0" IssueInstant="2017-08-30T16:15:22.397Z" Destination="https://mellon.example.com/mellon/postResponse" SignType="0" SignMethod="0">
        <saml:Issuer>https://rhsso.example.com:8443/auth/realms/ipa</saml:Issuer>
        <samlp:Status>
          <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success"/>
        </samlp:Status>
        <saml:Assertion xmlns="urn:oasis:names:tc:SAML:2.0:assertion" ID="ID_cf2298f8-981e-4c79-b173-cd3d8e43601b" IssueInstant="2017-08-30T16:15:22.396Z" Version="2.0">
          <saml:Issuer>https://rhsso.example.com:8443/auth/realms/ipa</saml:Issuer>
          <dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
            <dsig:SignedInfo>
              <dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
              <dsig:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>
              <dsig:Reference URI="#ID_cf2298f8-981e-4c79-b173-cd3d8e43601b">
                <dsig:Transforms>
                  <dsig:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>
                  <dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
                </dsig:Transforms>
                <dsig:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>
                <dsig:DigestValue>8OlYuzdYW/pu0OoNp9XFxRi1EETiNMZkgUpWOUJ/dG8=</dsig:DigestValue>
              </dsig:Reference>
            </dsig:SignedInfo>
            <dsig:SignatureValue>IuBZQ38BqtUc2Qbyy9BFj3x9BCfDQcoEoGFgOa//GFEwzOxunU9OxyZiod6cr1Z/0WgPeabX1GHJUwv//kf22FA8VLC1afErY4Yis9eUQUFUETyFRoFHjpou/rGz0NsEw4y8nTPN6p1je6jDM7Fo5cfSY8og6MY4rUdKOF2/rCCoFRJUC/UIFf8mUmOh8UIUNzPZqDc02Rw8nmGP2eHhHpWjDBalmzt+EL66tVqco3kRtQmPSIomkkJGh9vMGmHnu6n3k7I6SX8/h4bzuPurFB3eGhlxn9WKMQOdGphq4KKssij6yyZq2cM2fFLvZkrZSfLsDKjrpsf2YLC+Cmy5Ng==</dsig:SignatureValue>
            <dsig:KeyInfo>
              <dsig:KeyName>R2OGk9W0luNm_NtZbURWOrPlvFzSTDMimCVK5N1Mj5U</dsig:KeyName>
              <dsig:X509Data>
                <dsig:X509Certificate>MIIClTCCAX0CBgFeFdE9pDANBgkqhkiG9w0BAQsFADAOMQwwCgYDVQQDDANpcGEwHhcNMTcwODI0MTk1NDQ3WhcNMjcwODI0MTk1NjI3WjAOMQwwCgYDVQQDDANpcGEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgIPeag+JJmhtAkIGBwUT/req+jKC6c0Vl1Ngtzbcd07CP9mq1DomBkjuWl59J2urlEfrV4yT8avia0eYE6Dm/TqC74SHt3TVtiUliynAh/z2JvFlLb/EbGePSKrMnuNV8rV75YGcyE12vBRooUPx3hGaygsfaSOg+BijDuCSpbVdWSdVx9VecsWJfxSochOZUj6yvm/qTb8Ptl0x/o7/b/16GgjFRIKSFrdk8pVtMn1wCzpQQoGVHZmp1jrppGcp8KXIK54q7b4pPiTzlW6xhBgrmW2RtWQesCmN8ga1CVeBZKLsaH7argwGH5Ttz31iensqUO0degFu6nwCltgTVAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAFx8dl6RDle65q3IHIiGaL5fbJK5HxQiMXpk4N5riWQTP4g6xoTNAG4OFFUd4uRxt2ovdEdkbzhEy2lV4x626QdEfK5V9QKppupsTxTGA/4NMW9QCocAvFSpmYErmJIhfy6zzELoBK4Dpfcc3u1peHx2686msx6ExARF116d+5Xaps1dmPPy3yb2cCKzKbLhieqv+aLLrwz657ERUc4OnqEMEmmHFhHvPI7LRlS4AQ1/s1QlKcM9yqcu8WN3yKM/kuvZtZ0YTCSIl9W1b+I5v8wNoVFB22s7rfxs3DfJFaIImaTmRzaDX0MXgibEckrkigpO+anKe9B9z8CJdtlUHco=</dsig:X509Certificate>
              </dsig:X509Data>
              <dsig:KeyValue>
                <dsig:RSAKeyValue>
                  <dsig:Modulus>oCD3moPiSZobQJCBgcFE/63qvoygunNFZdTYLc23HdOwj/ZqtQ6JgZI7lpefSdrq5RH61eMk/Gr4mtHmBOg5v06gu+Eh7d01bYlJYspwIf89ibxZS2/xGxnj0iqzJ7jVfK1e+WBnMhNdrwUaKFD8d4RmsoLH2kjoPgYow7gkqW1XVknVcfVXnLFiX8UqHITmVI+sr5v6k2/D7ZdMf6O/2/9ehoIxUSCkha3ZPKVbTJ9cAs6UEKBlR2ZqdY66aRnKfClyCueKu2+KT4k85VusYQYK5ltkbVkHrApjfIGtQlXgWSi7Gh+2q4MBh+U7c99Ynp7KlDtHXoBbup8ApbYE1Q==</dsig:Modulus>
                  <dsig:Exponent>AQAB</dsig:Exponent>
                </dsig:RSAKeyValue>
              </dsig:KeyValue>
            </dsig:KeyInfo>
          </dsig:Signature>
          <saml:Subject>
            <saml:NameID Format="urn:oasis:names:tc:SAML:2.0:nameid-format:transient">G-e292fc24-74d9-4979-9f81-2c26d85174de</saml:NameID>
            <saml:SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:bearer">
              <saml:SubjectConfirmationData InResponseTo="_A65FF17C0924D19BE0FEC241B49EA45C" NotOnOrAfter="2017-08-30T16:20:20.396Z" Recipient="https://mellon.example.com/mellon/postResponse"/>
            </saml:SubjectConfirmation>
          </saml:Subject>
          <saml:Conditions NotBefore="2017-08-30T16:15:20.396Z" NotOnOrAfter="2017-08-30T16:16:20.396Z">
            <saml:AudienceRestriction>
              <saml:Audience>https://mellon.example.com/mellon/metadata</saml:Audience>
            </saml:AudienceRestriction>
          </saml:Conditions>
          <saml:AuthnStatement AuthnInstant="2017-08-30T16:15:22.397Z" SessionIndex="caa7c606-3404-4961-8af9-ba27345d1f7b">
            <saml:AuthnContext>
              <saml:AuthnContextClassRef>urn:oasis:names:tc:SAML:2.0:ac:classes:unspecified</saml:AuthnContextClassRef>
            </saml:AuthnContext>
          </saml:AuthnStatement>
          <saml:AttributeStatement>
            <saml:Attribute FriendlyName="List of groups user is a member of" Name="groups" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
              <saml:AttributeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">ipausers</saml:AttributeValue>
              <saml:AttributeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">openstack-users</saml:AttributeValue>
            </saml:Attribute>
            <saml:Attribute Name="Role" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
              <saml:AttributeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">view-profile</saml:AttributeValue>
            </saml:Attribute>
            <saml:Attribute Name="Role" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
              <saml:AttributeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">uma_authorization</saml:AttributeValue>
            </saml:Attribute>
            <saml:Attribute Name="Role" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic">
              <saml:AttributeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">manage-account</saml:AttributeValue>
            </saml:Attribute>
          </saml:AttributeStatement>
        </saml:Assertion>
        <saml:EncryptedAssertion>
          <xenc:EncryptedData Type="http://www.w3.org/2001/04/xmlenc#Element">
            <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc"/>
            <ds:KeyInfo>
              <xenc:EncryptedKey>
                <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p"/>
                <xenc:CipherData>
                  <xenc:CipherValue>m5GHJo1Za6Aejg0O7ZpCZleaNS45qzST8/0qFORoGjfLyNm0+lcquA7L2j/puCuVPWJ2jS4Y8P62iWYbhnATo7IPO3srpcfrAZaPtVlDKVp0ra8knx73h7NNIrbkWS63TZZNRh5OU5MgJRShHEpKq8fbRanRlq1iLODveKgw64W3XYr7vXbVT26/2NrrA7bkPLbK7YUyglmYDHN9PUbEKxKwQiBLnKNvaQgvBZaBPTzYTiBidM1Jllp/mj8QzfwiXCIAS/28iVmDCmjkSN6j33nDDLYU/Cq3rIGOWI8uQiw2oh2PlZi49T3400ffz2L9Tucdm/kjkTbhwWB3b5A1YQ==</xenc:CipherValue>
                </xenc:CipherData>
              </xenc:EncryptedKey>
            </ds:KeyInfo>
            <xenc:CipherData>
              <xenc:CipherValue>[encoded data, 7404 characters]</xenc:CipherValue>
            </xenc:CipherData>
          </xenc:EncryptedData>
        </saml:EncryptedAssertion>
      </samlp:Response>
    am_new_request_session id=9cf3ebac4e542827e276dc064ce8c4e4 cookie_token="Name='mellon-cookie' Domain='mellon.example.com' Path='/'"
    am_cache_new created new session, id=9cf3ebac4e542827e276dc064ce8c4e4 at 2017-08-30T16:15:23Z cookie_token="Name='mellon-cookie' Domain='mellon.example.com' Path='/'"
    am_handle_session_expire failed to find Assertion.AuthnStatement.SessionNotOnOrAfter
    add_attributes name=groups value=ipausers
    add_attributes name=groups value=openstack-users
    add_attributes name=Role value=view-profile
    add_attributes name=Role value=uma_authorization
    add_attributes name=Role value=manage-account
    [APLOG_DEBUG auth_mellon_handler.c:549] The current LassoProfile object doesn't contain a LassoIdentity object.
    === Response ===
    Status: 303 See Other(303)
    user: (null) auth_type=(null)
    Response Headers:
      Cache-Control: private, max-age=0, must-revalidate
      Set-Cookie: mellon-cookie=9cf3ebac4e542827e276dc064ce8c4e4; Version=1; Path=/; Domain=mellon.example.com;
      Location: https://mellon.example.com/saml-test/protected.html
      Content-Length: 258
      Keep-Alive: timeout=5, max=100
      Connection: Keep-Alive
      Content-Type: text/html; charset=iso-8859-1
    Response Error Headers:
    Environment:
      UNIQUE_ID: Wabkm2fzHRm5EyVgPZnqEAAAAAU
      HTTPS: on
      SSL_TLS_SNI: mellon.example.com
    ---------------------------------- New Request ---------------------------------
    GET - /saml-test/protected.html
    log_id: (null)
    server: name=/etc/httpd/conf.d/ssl.conf, scheme=https hostname=mellon.example.com port=443
    pid: 21593, tid: 140251630954624
    unparsed_uri: /saml-test/protected.html
    uri: /saml-test/protected.html
    path_info:
    filename: /var/www/html/saml-test/protected.html
    query args: (null)
    Request Headers:
      Host: mellon.example.com
      Connection: keep-alive
      Cache-Control: max-age=0
      Upgrade-Insecure-Requests: 1
      User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36
      Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
      DNT: 1
      Referer: https://rhsso.example.com:8443/auth/realms/ipa/login-actions/authenticate?code=qv8kqt2kFiT0YBmG8TIzcNzgxfFp6q_N15M5pS931Eo.caa7c606-3404-4961-8af9-ba27345d1f7b&execution=10aa0b63-d5d9-4960-8ad8-16720df6fc8e
      Accept-Encoding: gzip, deflate, br
      Accept-Language: en-US,en;q=0.8
      Cookie: mellon-cookie=9cf3ebac4e542827e276dc064ce8c4e4
    Mellon Directory Configuration for URL: /saml-test/protected.html
      MellonEnable (enable): auth
      MellonVariable (varname): cookie
      MellonSecureCookie (secure): Off
      MellonMergeEnvVars (merge_env_vars): (null)
      MellonEnvVarsIndexStart (env_vars_index_start): -1
      MellonEnvVarsSetCount (env_vars_count_in_n): On
      MellonCookieDomain (cookie_domain): (null)
      MellonCookiePath (cookie_path): (null)
      MellonCond (cond): 0 items
      MellonSetEnv (envattr): 0 items
      MellonUser (userattr): NAME_ID
      MellonIdP (idpattr): IDP
      MellonSessionDump (dump_session): Off
      MellonSamlResponseDump (dump_saml_response): Off
      MellonEndpointPath (endpoint_path): /mellon/
      MellonSPMetadataFile (sp_metadata_file):
        pathname: "/etc/httpd/saml2/demo_sp_metadata.xml"
          <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
          <EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
                            xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
                            xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
                            entityID="https://mellon.example.com/mellon/metadata">
           <SPSSODescriptor
             AuthnRequestsSigned="true"
             WantAssertionsSigned="true"
             protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
             <KeyDescriptor use="signing">
               <ds:KeyInfo>
                 <ds:X509Data>
                   <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
                 </ds:X509Data>
               </ds:KeyInfo>
             </KeyDescriptor>
             <KeyDescriptor use="encryption">
               <ds:KeyInfo>
                 <ds:X509Data>
                   <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
                 </ds:X509Data>
               </ds:KeyInfo>
             </KeyDescriptor>
             <SingleLogoutService
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
               Location="https://mellon.example.com/mellon/logout" />
             <SingleLogoutService
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
               Location="https://mellon.example.com/mellon/logout" />
             <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
             <AssertionConsumerService
               index="0"
               isDefault="true"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
               Location="https://mellon.example.com/mellon/postResponse" />
             <AssertionConsumerService
               index="1"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact"
               Location="https://mellon.example.com/mellon/artifactResponse" />
             <AssertionConsumerService
               index="2"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:PAOS"
               Location="https://mellon.example.com/mellon/paosResponse" />
           </SPSSODescriptor>
          </EntityDescriptor>
      MellonSPPrivateKeyFile (sp_private_key_file):
        pathname: "/etc/httpd/saml2/demo.key"
          -----BEGIN PRIVATE KEY-----
          MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQDHUXILDtuMxyFP
          6OW81hqfj9z+gC7sxR6U8bRPI4gFiNjkNF+4HMyrKtVtfwA5WJ1tJ4IaZbg4fGap
          iCcWQ5tjjuZ7CpZ6XLekq63OGrkgZxNm8L+AjvREv78iR4Myc4x6ybN1LwQnV+oD
          F0i9SAEPnfJCaCA+1+DC3RKy7+xtK3SVimUWwAHmkNU6N0wCVSNYn1KgnxBSCPTx
          2DifbyRl21SiokCfLSnktE++WBzRzldSxzMrkSfFoS7/uT232tbdw2NsJmHGLRGk
          myBrEC6BVhQ746NM1cLDtrOots7bNfZ3yfb3W1tpoKVOhM2se3OTKdidAQsaGlVu
          7QIhBqinAgMBAAECggEBAJtU662WfJ9vqJRgCnpp2QG02iM0vl0jGbw1ybFLHXxC
          s9TUxCv1tcNHdGEK8p++YaFpgskTsMfEmzVPuDZvpa+m9BO7op3ll/CrIp5W0SNh
          cQtuX6/OuKrDTC9oz+QHjNk8S7DtXS1UJDkYckWg0cLb8qqx/z86eh0isKnmtLg2
          H1+6L6mB9fcZldkcrU+kXT+dcDX85skMZAeBsrG4yaoX26AzVl8lEl2rJAQvpxj8
          5wGBC4riWY6TzMYiCjcS5JfZIlbhcZe61ej3A48NVBSKCP1XKo0xbKuOHIQuMeeW
          wSaboBwRzJ9JdTXlq5UWfLvmjXDc/HCwk/N7cj021uECgYEA5KkQr3cSKrMIkYoO
          H0Vnkw1kYYGUjtTL00Nfdkv7uGMF122nyt1ND0gpdS0jgNx3LSEam/gY35UWEjGH
          i8DGD04k8pvKDUsl8cuYPcC3oce1lLCGAnw+aHPC5wtA829CLOLtBfxXIhVAI0tp
          ECosD/A63/m1LC19XolOd10/PC8CgYEA3yZChEYZupDGJFZltiy0ZgUarvD2Ss4N
          QiRVR+CmpBrOKZdD8q6uUuqWQN9Rw7kXm8LxAPYwiIDVjxjYALF+j7/9Q1oZyKuv
          eHJdMe4eRUeqeaIKbxnFfKwGZ5rj97jwPrkUCxio75KZhpOcDHMSgBCBtzW0XIZl
          gTeQYOshZQkCgYB5TK6LRnEesabj/gaL1DejrMEJcMIsGvqdceocSSaZo/4fUA5o
          8YjFiJRlkrJ403ttN1h0UOJxCReSQzASlQr8Z4n2IWrILotMf6Kdb7R6YAUVgac1
          fk9k/bPw+OlVujmyshbmy/w1GmzRzFlJt/Vz5w50bnULoH4XPmOfspmvBQKBgBcJ
          rihVzGY0eCBcQxfxuZYmxMB25BaI+1luwtcu3EVo9wvYMA2n9xtcWLLN23UncMaF
          87ezswMEugeR+wrnSDezDISdkrfi8bSvqetzt/BTG8h+8DDUKk1avTaJCSwUDcmL
          9gPHQfmp2uvH5X5riudpzNqLUtmSjnwurlszKzlxAoGAR8STlDJhNph+p3cF8k25
          ydT1kypxnjzVG8CAV5/h3dUmc7j7gyV8NlWZfWacxMZWOBsrdVh0zhMNUPiLJaGd
          I1isOkmiN9JFYMMhHSnhPnTCIjmu6uBLxf8wotHAvzWOJPV7lUZbw21KIN3DS79F
          sGZ2QzGYn4inHG4UHClhZxU=
          -----END PRIVATE KEY-----
      MellonSPCertFile (sp_cert_file):
        pathname: "/etc/httpd/saml2/demo.cert"
          -----BEGIN CERTIFICATE-----
          MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=
          -----END CERTIFICATE-----
      MellonIdPPublicKeyFile (idp_public_key_file):
        file_data: NULL
      MellonIdPCAFile (idp_ca_file):
        file_data: NULL
      MellonIdPMetadataFile (idp_metadata): 1 items
      [ 0] Metadata
        pathname: "/etc/httpd/saml2/demo_keycloak_ipa_idp_metadata.xml"
          <?xml version="1.0" encoding="UTF-8"?>
          <!--
            ~ Copyright 2016 Red Hat, Inc. and/or its affiliates
            ~ and other contributors as indicated by the @author tags.
            ~
            ~ Licensed under the Apache License, Version 2.0 (the "License");
            ~ you may not use this file except in compliance with the License.
            ~ You may obtain a copy of the License at
            ~
            ~ http://www.apache.org/licenses/LICENSE-2.0
            ~
            ~ Unless required by applicable law or agreed to in writing, software
            ~ distributed under the License is distributed on an "AS IS" BASIS,
            ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
            ~ See the License for the specific language governing permissions and
            ~ limitations under the License.
            -->

          <EntitiesDescriptor Name="urn:keycloak" xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
          					xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
          	<EntityDescriptor entityID="https://rhsso.example.com:8443/auth/realms/ipa">
          		<IDPSSODescriptor WantAuthnRequestsSigned="true"
          			protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
                                  <KeyDescriptor use="signing">
                                    <dsig:KeyInfo>
                                      <dsig:KeyName>R2OGk9W0luNm_NtZbURWOrPlvFzSTDMimCVK5N1Mj5U</dsig:KeyName>
                                      <dsig:X509Data>
                                        <dsig:X509Certificate>MIIClTCCAX0CBgFeFdE9pDANBgkqhkiG9w0BAQsFADAOMQwwCgYDVQQDDANpcGEwHhcNMTcwODI0MTk1NDQ3WhcNMjcwODI0MTk1NjI3WjAOMQwwCgYDVQQDDANpcGEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgIPeag+JJmhtAkIGBwUT/req+jKC6c0Vl1Ngtzbcd07CP9mq1DomBkjuWl59J2urlEfrV4yT8avia0eYE6Dm/TqC74SHt3TVtiUliynAh/z2JvFlLb/EbGePSKrMnuNV8rV75YGcyE12vBRooUPx3hGaygsfaSOg+BijDuCSpbVdWSdVx9VecsWJfxSochOZUj6yvm/qTb8Ptl0x/o7/b/16GgjFRIKSFrdk8pVtMn1wCzpQQoGVHZmp1jrppGcp8KXIK54q7b4pPiTzlW6xhBgrmW2RtWQesCmN8ga1CVeBZKLsaH7argwGH5Ttz31iensqUO0degFu6nwCltgTVAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAFx8dl6RDle65q3IHIiGaL5fbJK5HxQiMXpk4N5riWQTP4g6xoTNAG4OFFUd4uRxt2ovdEdkbzhEy2lV4x626QdEfK5V9QKppupsTxTGA/4NMW9QCocAvFSpmYErmJIhfy6zzELoBK4Dpfcc3u1peHx2686msx6ExARF116d+5Xaps1dmPPy3yb2cCKzKbLhieqv+aLLrwz657ERUc4OnqEMEmmHFhHvPI7LRlS4AQ1/s1QlKcM9yqcu8WN3yKM/kuvZtZ0YTCSIl9W1b+I5v8wNoVFB22s7rfxs3DfJFaIImaTmRzaDX0MXgibEckrkigpO+anKe9B9z8CJdtlUHco=</dsig:X509Certificate>
                                      </dsig:X509Data>
                                    </dsig:KeyInfo>
                                  </KeyDescriptor>

          			<SingleLogoutService
          					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
          					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleLogoutService
          					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
          					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</NameIDFormat>
          			<SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleSignOnService
          				Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleSignOnService
          				Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          		</IDPSSODescriptor>
          	</EntityDescriptor>
          </EntitiesDescriptor>
      [ 0] Chain File
        file_data: NULL
      MellonIdPIgnore (idp_ignore):
      MellonSPentityId (sp_entity_id): (null)
      MellonOrganizationName (sp_org_name): 0 items
      MellonOrganizationDisplayName (sp_org_display_name): 0 items
      MellonOrganizationURL (sp_org_url): 0 items
      MellonSessionLength (session_length): -1
      MellonNoCookieErrorPage (no_cookie_error_page): (null)
      MellonNoSuccessErrorPage (no_success_error_page): (null)
      MellonDefaultLoginPath (login_path): /
      MellonDiscoveryURL (discovery_url): (null)
      MellonProbeDiscoveryTimeout (probe_discovery_timeout): -1
      MellonProbeDiscoveryIdP (probe_discovery_idp): 0 items
      MellonAuthnContextClassRef (authn_context_class_ref): 0 items
      MellonSubjectConfirmationDataAddressCheck (subject_confirmation_data_address_check): On
      MellonDoNotVerifyLogoutSignature (do_not_verify_logout_signature): 0 items
      MellonPostReplay (post_replay): On
      MellonECPSendIDPList (ecp_send_idplist): On
    enter function am_auth_mellon_user
    searching for session with key 9cf3ebac4e542827e276dc064ce8c4e4 (session) ... found.
    Session Cache Entry
      key: 9cf3ebac4e542827e276dc064ce8c4e4
      name_id: G-e292fc24-74d9-4979-9f81-2c26d85174de
      expires: 2017-08-31T16:15:23Z
      access: 2017-08-30T16:15:23Z
      logged_in: True
    am_auth_mellon_user am_enable_auth, have valid session
    am_check_permissions succeeds

    === Response ===
    Status: 200 OK(200)
    user: G-e292fc24-74d9-4979-9f81-2c26d85174de auth_type=Mellon
    Response Headers:
      Cache-Control: private, max-age=0, must-revalidate
      Last-Modified: Mon, 28 Aug 2017 15:15:18 GMT
      ETag: "4a-557d1c33a4519"
      Accept-Ranges: bytes
      Content-Length: 74
      Keep-Alive: timeout=5, max=99
      Connection: Keep-Alive
      Content-Type: text/html; charset=UTF-8
    Response Error Headers:
      Cache-Control: private, max-age=0, must-revalidate
    Environment:
      UNIQUE_ID: Wabkm2fzHRm5EyVgPZnqEQAAAAU
      MELLON_NAME_ID: G-e292fc24-74d9-4979-9f81-2c26d85174de
      MELLON_NAME_ID_0: G-e292fc24-74d9-4979-9f81-2c26d85174de
      MELLON_groups: ipausers
      MELLON_groups_0: ipausers
      MELLON_groups_1: openstack-users
      MELLON_Role: view-profile
      MELLON_Role_0: view-profile
      MELLON_Role_1: uma_authorization
      MELLON_Role_2: manage-account
      MELLON_IDP: https://rhsso.example.com:8443/auth/realms/ipa
      MELLON_IDP_0: https://rhsso.example.com:8443/auth/realms/ipa
      HTTPS: on
      SSL_TLS_SNI: mellon.example.com
    ---------------------------------- New Request ---------------------------------
    GET - /favicon.ico
    log_id: (null)
    server: name=/etc/httpd/conf.d/ssl.conf, scheme=https hostname=mellon.example.com port=443
    pid: 21593, tid: 140251630954624
    unparsed_uri: /favicon.ico
    uri: /favicon.ico
    path_info:
    filename: /var/www/html/favicon.ico
    query args: (null)
    Request Headers:
      Host: mellon.example.com
      Connection: keep-alive
      User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36
      Accept: image/webp,image/apng,image/*,*/*;q=0.8
      DNT: 1
      Referer: https://mellon.example.com/saml-test/protected.html
      Accept-Encoding: gzip, deflate, br
      Accept-Language: en-US,en;q=0.8
      Cookie: mellon-cookie=9cf3ebac4e542827e276dc064ce8c4e4
    Mellon Directory Configuration for URL: /favicon.ico
      MellonEnable (enable): info
      MellonVariable (varname): cookie
      MellonSecureCookie (secure): Off
      MellonMergeEnvVars (merge_env_vars): (null)
      MellonEnvVarsIndexStart (env_vars_index_start): -1
      MellonEnvVarsSetCount (env_vars_count_in_n): On
      MellonCookieDomain (cookie_domain): (null)
      MellonCookiePath (cookie_path): (null)
      MellonCond (cond): 0 items
      MellonSetEnv (envattr): 0 items
      MellonUser (userattr): NAME_ID
      MellonIdP (idpattr): IDP
      MellonSessionDump (dump_session): Off
      MellonSamlResponseDump (dump_saml_response): Off
      MellonEndpointPath (endpoint_path): /mellon/
      MellonSPMetadataFile (sp_metadata_file):
        pathname: "/etc/httpd/saml2/demo_sp_metadata.xml"
          <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
          <EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
                            xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
                            xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
                            entityID="https://mellon.example.com/mellon/metadata">
           <SPSSODescriptor
             AuthnRequestsSigned="true"
             WantAssertionsSigned="true"
             protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
             <KeyDescriptor use="signing">
               <ds:KeyInfo>
                 <ds:X509Data>
                   <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
                 </ds:X509Data>
               </ds:KeyInfo>
             </KeyDescriptor>
             <KeyDescriptor use="encryption">
               <ds:KeyInfo>
                 <ds:X509Data>
                   <ds:X509Certificate>MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=</ds:X509Certificate>
                 </ds:X509Data>
               </ds:KeyInfo>
             </KeyDescriptor>
             <SingleLogoutService
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
               Location="https://mellon.example.com/mellon/logout" />
             <SingleLogoutService
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
               Location="https://mellon.example.com/mellon/logout" />
             <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
             <AssertionConsumerService
               index="0"
               isDefault="true"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
               Location="https://mellon.example.com/mellon/postResponse" />
             <AssertionConsumerService
               index="1"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact"
               Location="https://mellon.example.com/mellon/artifactResponse" />
             <AssertionConsumerService
               index="2"
               Binding="urn:oasis:names:tc:SAML:2.0:bindings:PAOS"
               Location="https://mellon.example.com/mellon/paosResponse" />
           </SPSSODescriptor>
          </EntityDescriptor>
      MellonSPPrivateKeyFile (sp_private_key_file):
        pathname: "/etc/httpd/saml2/demo.key"
          -----BEGIN PRIVATE KEY-----
          MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQDHUXILDtuMxyFP
          6OW81hqfj9z+gC7sxR6U8bRPI4gFiNjkNF+4HMyrKtVtfwA5WJ1tJ4IaZbg4fGap
          iCcWQ5tjjuZ7CpZ6XLekq63OGrkgZxNm8L+AjvREv78iR4Myc4x6ybN1LwQnV+oD
          F0i9SAEPnfJCaCA+1+DC3RKy7+xtK3SVimUWwAHmkNU6N0wCVSNYn1KgnxBSCPTx
          2DifbyRl21SiokCfLSnktE++WBzRzldSxzMrkSfFoS7/uT232tbdw2NsJmHGLRGk
          myBrEC6BVhQ746NM1cLDtrOots7bNfZ3yfb3W1tpoKVOhM2se3OTKdidAQsaGlVu
          7QIhBqinAgMBAAECggEBAJtU662WfJ9vqJRgCnpp2QG02iM0vl0jGbw1ybFLHXxC
          s9TUxCv1tcNHdGEK8p++YaFpgskTsMfEmzVPuDZvpa+m9BO7op3ll/CrIp5W0SNh
          cQtuX6/OuKrDTC9oz+QHjNk8S7DtXS1UJDkYckWg0cLb8qqx/z86eh0isKnmtLg2
          H1+6L6mB9fcZldkcrU+kXT+dcDX85skMZAeBsrG4yaoX26AzVl8lEl2rJAQvpxj8
          5wGBC4riWY6TzMYiCjcS5JfZIlbhcZe61ej3A48NVBSKCP1XKo0xbKuOHIQuMeeW
          wSaboBwRzJ9JdTXlq5UWfLvmjXDc/HCwk/N7cj021uECgYEA5KkQr3cSKrMIkYoO
          H0Vnkw1kYYGUjtTL00Nfdkv7uGMF122nyt1ND0gpdS0jgNx3LSEam/gY35UWEjGH
          i8DGD04k8pvKDUsl8cuYPcC3oce1lLCGAnw+aHPC5wtA829CLOLtBfxXIhVAI0tp
          ECosD/A63/m1LC19XolOd10/PC8CgYEA3yZChEYZupDGJFZltiy0ZgUarvD2Ss4N
          QiRVR+CmpBrOKZdD8q6uUuqWQN9Rw7kXm8LxAPYwiIDVjxjYALF+j7/9Q1oZyKuv
          eHJdMe4eRUeqeaIKbxnFfKwGZ5rj97jwPrkUCxio75KZhpOcDHMSgBCBtzW0XIZl
          gTeQYOshZQkCgYB5TK6LRnEesabj/gaL1DejrMEJcMIsGvqdceocSSaZo/4fUA5o
          8YjFiJRlkrJ403ttN1h0UOJxCReSQzASlQr8Z4n2IWrILotMf6Kdb7R6YAUVgac1
          fk9k/bPw+OlVujmyshbmy/w1GmzRzFlJt/Vz5w50bnULoH4XPmOfspmvBQKBgBcJ
          rihVzGY0eCBcQxfxuZYmxMB25BaI+1luwtcu3EVo9wvYMA2n9xtcWLLN23UncMaF
          87ezswMEugeR+wrnSDezDISdkrfi8bSvqetzt/BTG8h+8DDUKk1avTaJCSwUDcmL
          9gPHQfmp2uvH5X5riudpzNqLUtmSjnwurlszKzlxAoGAR8STlDJhNph+p3cF8k25
          ydT1kypxnjzVG8CAV5/h3dUmc7j7gyV8NlWZfWacxMZWOBsrdVh0zhMNUPiLJaGd
          I1isOkmiN9JFYMMhHSnhPnTCIjmu6uBLxf8wotHAvzWOJPV7lUZbw21KIN3DS79F
          sGZ2QzGYn4inHG4UHClhZxU=
          -----END PRIVATE KEY-----
      MellonSPCertFile (sp_cert_file):
        pathname: "/etc/httpd/saml2/demo.cert"
          -----BEGIN CERTIFICATE-----
          MIIDDTCCAfWgAwIBAgIJALnqrR7yvGH5MA0GCSqGSIb3DQEBCwUAMB0xGzAZBgNV
          BAMMEm1lbGxvbi5leGFtcGxlLmNvbTAeFw0xNzA4MjgxNTExNDlaFw0yMjA4Mjcx
          NTExNDlaMB0xGzAZBgNVBAMMEm1lbGxvbi5leGFtcGxlLmNvbTCCASIwDQYJKoZI
          hvcNAQEBBQADggEPADCCAQoCggEBAMdRcgsO24zHIU/o5bzWGp+P3P6ALuzFHpTx
          tE8jiAWI2OQ0X7gczKsq1W1/ADlYnW0nghpluDh8ZqmIJxZDm2OO5nsKlnpct6Sr
          rc4auSBnE2bwv4CO9ES/vyJHgzJzjHrJs3UvBCdX6gMXSL1IAQ+d8kJoID7X4MLd
          ErLv7G0rdJWKZRbAAeaQ1To3TAJVI1ifUqCfEFII9PHYOJ9vJGXbVKKiQJ8tKeS0
          T75YHNHOV1LHMyuRJ8WhLv+5Pbfa1t3DY2wmYcYtEaSbIGsQLoFWFDvjo0zVwsO2
          s6i2zts19nfJ9vdbW2mgpU6Ezax7c5Mp2J0BCxoaVW7tAiEGqKcCAwEAAaNQME4w
          HQYDVR0OBBYEFDBbq0pjLeMFPcBt7A++c90lSM5vMB8GA1UdIwQYMBaAFDBbq0pj
          LeMFPcBt7A++c90lSM5vMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQELBQADggEB
          AFiIxqhW37Td/rD77N648feciigEk/GW4zsqxdx9MspnvSTfr0/lPPOaVhd/UGAw
          g+DwGOmqfisvl44wg07y+4T0NTDzvgkrT0ON5hyEBucFhSjPN+lhwWaH422URwUL
          cKTqkrnAk4Er4bSi1GhsV/2/Xv2ZYyJCcUeiwWQ2fEZXp4ke3IZPN0nYlajKzBTd
          Bv9YlynXKuO1hxBYDWQrrjpp1UZRKjJD2nLUsTi8oFuLhB/RwUMqXZ0nFuNoOkDQ
          XotXjsiL1KtqNW1k/oVtLwNP0trqqh9npWV+R3pDTckxIHQhOvs5VqQZANViH6mp
          YK53b9Bhr0TpIOKetFY68kQ=
          -----END CERTIFICATE-----
      MellonIdPPublicKeyFile (idp_public_key_file):
        file_data: NULL
      MellonIdPCAFile (idp_ca_file):
        file_data: NULL
      MellonIdPMetadataFile (idp_metadata): 1 items
      [ 0] Metadata
        pathname: "/etc/httpd/saml2/demo_keycloak_ipa_idp_metadata.xml"
          <?xml version="1.0" encoding="UTF-8"?>
          <!--
            ~ Copyright 2016 Red Hat, Inc. and/or its affiliates
            ~ and other contributors as indicated by the @author tags.
            ~
            ~ Licensed under the Apache License, Version 2.0 (the "License");
            ~ you may not use this file except in compliance with the License.
            ~ You may obtain a copy of the License at
            ~
            ~ http://www.apache.org/licenses/LICENSE-2.0
            ~
            ~ Unless required by applicable law or agreed to in writing, software
            ~ distributed under the License is distributed on an "AS IS" BASIS,
            ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
            ~ See the License for the specific language governing permissions and
            ~ limitations under the License.
            -->

          <EntitiesDescriptor Name="urn:keycloak" xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
          					xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
          	<EntityDescriptor entityID="https://rhsso.example.com:8443/auth/realms/ipa">
          		<IDPSSODescriptor WantAuthnRequestsSigned="true"
          			protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
                                  <KeyDescriptor use="signing">
                                    <dsig:KeyInfo>
                                      <dsig:KeyName>R2OGk9W0luNm_NtZbURWOrPlvFzSTDMimCVK5N1Mj5U</dsig:KeyName>
                                      <dsig:X509Data>
                                        <dsig:X509Certificate>MIIClTCCAX0CBgFeFdE9pDANBgkqhkiG9w0BAQsFADAOMQwwCgYDVQQDDANpcGEwHhcNMTcwODI0MTk1NDQ3WhcNMjcwODI0MTk1NjI3WjAOMQwwCgYDVQQDDANpcGEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgIPeag+JJmhtAkIGBwUT/req+jKC6c0Vl1Ngtzbcd07CP9mq1DomBkjuWl59J2urlEfrV4yT8avia0eYE6Dm/TqC74SHt3TVtiUliynAh/z2JvFlLb/EbGePSKrMnuNV8rV75YGcyE12vBRooUPx3hGaygsfaSOg+BijDuCSpbVdWSdVx9VecsWJfxSochOZUj6yvm/qTb8Ptl0x/o7/b/16GgjFRIKSFrdk8pVtMn1wCzpQQoGVHZmp1jrppGcp8KXIK54q7b4pPiTzlW6xhBgrmW2RtWQesCmN8ga1CVeBZKLsaH7argwGH5Ttz31iensqUO0degFu6nwCltgTVAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAFx8dl6RDle65q3IHIiGaL5fbJK5HxQiMXpk4N5riWQTP4g6xoTNAG4OFFUd4uRxt2ovdEdkbzhEy2lV4x626QdEfK5V9QKppupsTxTGA/4NMW9QCocAvFSpmYErmJIhfy6zzELoBK4Dpfcc3u1peHx2686msx6ExARF116d+5Xaps1dmPPy3yb2cCKzKbLhieqv+aLLrwz657ERUc4OnqEMEmmHFhHvPI7LRlS4AQ1/s1QlKcM9yqcu8WN3yKM/kuvZtZ0YTCSIl9W1b+I5v8wNoVFB22s7rfxs3DfJFaIImaTmRzaDX0MXgibEckrkigpO+anKe9B9z8CJdtlUHco=</dsig:X509Certificate>
                                      </dsig:X509Data>
                                    </dsig:KeyInfo>
                                  </KeyDescriptor>

          			<SingleLogoutService
          					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
          					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleLogoutService
          					Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
          					Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat>
          			<NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</NameIDFormat>
          			<SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleSignOnService
          				Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          			<SingleSignOnService
          				Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP"
          				Location="https://rhsso.example.com:8443/auth/realms/ipa/protocol/saml" />
          		</IDPSSODescriptor>
          	</EntityDescriptor>
          </EntitiesDescriptor>
      [ 0] Chain File
        file_data: NULL
      MellonIdPIgnore (idp_ignore):
      MellonSPentityId (sp_entity_id): (null)
      MellonOrganizationName (sp_org_name): 0 items
      MellonOrganizationDisplayName (sp_org_display_name): 0 items
      MellonOrganizationURL (sp_org_url): 0 items
      MellonSessionLength (session_length): -1
      MellonNoCookieErrorPage (no_cookie_error_page): (null)
      MellonNoSuccessErrorPage (no_success_error_page): (null)
      MellonDefaultLoginPath (login_path): /
      MellonDiscoveryURL (discovery_url): (null)
      MellonProbeDiscoveryTimeout (probe_discovery_timeout): -1
      MellonProbeDiscoveryIdP (probe_discovery_idp): 0 items
      MellonAuthnContextClassRef (authn_context_class_ref): 0 items
      MellonSubjectConfirmationDataAddressCheck (subject_confirmation_data_address_check): On
      MellonDoNotVerifyLogoutSignature (do_not_verify_logout_signature): 0 items
      MellonPostReplay (post_replay): On
      MellonECPSendIDPList (ecp_send_idplist): On
    enter function am_auth_mellon_user
    searching for session with key 9cf3ebac4e542827e276dc064ce8c4e4 (session) ... found.
    Session Cache Entry
      key: 9cf3ebac4e542827e276dc064ce8c4e4
      name_id: G-e292fc24-74d9-4979-9f81-2c26d85174de
      expires: 2017-08-31T16:15:23Z
      access: 2017-08-30T16:15:23Z
      logged_in: True
    am_check_permissions succeeds
    am_auth_mellon_user am_enable_info, have valid session

    === Response ===
    Status: 404 Not Found(404)
    user: G-e292fc24-74d9-4979-9f81-2c26d85174de auth_type=Mellon
    Response Headers:
      Cache-Control: private, max-age=0, must-revalidate
      Content-Length: 209
      Keep-Alive: timeout=5, max=98
      Connection: Keep-Alive
      Content-Type: text/html; charset=iso-8859-1
    Response Error Headers:
    Environment:
      UNIQUE_ID: WabknGfzHRm5EyVgPZnqEgAAAAU
      MELLON_NAME_ID: G-e292fc24-74d9-4979-9f81-2c26d85174de
      MELLON_NAME_ID_0: G-e292fc24-74d9-4979-9f81-2c26d85174de
      MELLON_groups: ipausers
      MELLON_groups_0: ipausers
      MELLON_groups_1: openstack-users
      MELLON_Role: view-profile
      MELLON_Role_0: view-profile
      MELLON_Role_1: uma_authorization
      MELLON_Role_2: manage-account
      MELLON_IDP: https://rhsso.example.com:8443/auth/realms/ipa
      MELLON_IDP_0: https://rhsso.example.com:8443/auth/realms/ipa
      HTTPS: on
      SSL_TLS_SNI: mellon.example.com

1. When you are protecting just one location with Mellon there isn’t much added value in splitting the configuration directives. But when you need to protect many distinct locations it’s repetitive and error prone to cut and paste common values in each `<Location>` block. It makes maintaining the configuration that much more difficult because you will need to edit each and every `<Location>` directive to change something like the name of a metadata file. This is why Mellon configuration often groups common values in a location that can be shared by all descendants. Using the `/` root location is the most obvious example but the same idea can be applied to complex trees.