Integrating server applications with multiple authentication providers

A method, comprising:

• receiving, at an application running on a hardware processor, a response from a partner application, the response comprising a header having a realm parameter and an application identifier parameter;
• concatenating the partner application identifier with the realm parameter to create a concatenated value;
• determining whether the concatenated value matches an entry in a list of configured partner applications;
• creating a self-issued token for the partner application or for an authentication issuer in response to determining that there is a match;
• in response to determining that there is no match, determining whether a realm value in the response matches a configured authentication issuer;
• and
• using a tenant identifier to generate a self-issued token for the authentication issuer, wherein an approved authentication issuer configuration identifies a Globally Unique Identifier (GUID) for an approved authentication issuer and identifies the tenant identifier when an application is configured for an on-premise installation.

A computer system, comprising:

• one or more processor devices;
• system memory;
• one or more computer-readable storage media having stored thereon computer-executable instructions that, when executed by the one or more processors, causes the processors to perform a method for generating authentication credentials, the processor operating to:
• send a request from a first application to a second application;
• receive a response to the request, the response comprising a list of authentication issuers trusted by the second application;
• compare the list of authentication issuers trusted by the second application to a list of authentication issuers approved for the first application;
• and
• identify an authentication issuer that matches both lists;
• construct a token for an authentication issuer using a tenant identifier from an approved authentication issuer configuration;
• obtain authentication credentials from the authentication issuer using the token;
• and
• generate a revised request to the second application using the authentication credentials;
• in response to determining that there is no match, determining whether a realm value in the response matches a configured authentication issuer;
• and
• using the tenant identifier to generate a self-issued token for the authentication issuer,
• wherein an approved authentication issuer configuration identifies a Globally Unique Identifier (GUID) for an approved authentication issuer and identifies the tenant identifier when an application is configured for an on-premise installation.