Systems, methods, and storage media for administration of identity management systems within an identity infrastructure

1 . A system configured for controlling access to an application in an identity infrastructure, the system comprising:

one or more hardware processors configured by machine-readable instructions to:

request to access the application, wherein the application is associated with an identity system;

determine a status of the identity system, the status comprising one of an available status and an unavailable status, and when the status comprises the unavailable status,

transmit a request for additional information,

receive the additional information, and

verify the additional information by referencing an identity cache associated with the identity system;

authenticate a user to access the application when at least one of:

the status comprises the available status, and

the additional information has been verified;

in response to authenticating the user at the application, send a communication from the application to the user, granting the user access to the application; and

store a subset of at least one of identity metadata and identity data associated with a plurality of users, including at least the user, to the identity cache, wherein the identity cache is at least one of electronically, logistically, logically, and communicatively coupled to the identity system and an orchestrating agent.

2 . The system of claim 1 , wherein,

requesting to access the application comprises receiving the request at the orchestrating agent prior to determining a status of the identity system;

determining a status of the identity system comprises using the orchestrating agent to determine the status of the identity system; and

when the status comprises the available status, authenticating the user comprises:

receiving at least some identity data at the identity system from the user,

authenticating the user at the identity system based at least in part on the at least some identity data, and

receiving a user authentication confirmation at the orchestrating agent.

3 . The system of claim 2 , wherein,

verifying the additional information by referencing an identity cache comprises using the orchestrating agent to reference the identity cache associated with the identity system; and

authenticating a user to access the application comprises creating a token at the orchestrating agent, wherein,

the token is created based on one of:

receiving the user authentication confirmation at the orchestrating agent, and

referencing the identity cache associated with the identity system using the orchestrating agent to reference the identity cache associated with the identity system.

4 . The system of claim 3 , wherein, in response to authenticating the user at the application, the one or more hardware processors are further configured by machine-readable instructions to: create a user session with the application.

5 . The system of claim 3 , wherein,

the at least some identity data comprises at least one of a user identifier, a username, and a password; and

the identity system creates a first identity session based at least in part on authenticating the user at the identity system.

6 . The system of claim 5 , wherein prior to creating the token at the orchestrating agent, the one or more hardware processors are configured by machine-readable instructions to: provide the orchestrating agent with information pertaining to the first identity session; and create, at the orchestrating agent, a second identity session, wherein the second identity session is created in response to the first identity session.

7 . The system of claim 1 , wherein transmitting the request for additional information comprises one or more of:

requesting at least some identity data from the user, the at least some identity data including at least a username and password;

requesting answers to one or more security questions; and

requesting additional identity data from the user, wherein the additional identity data comprises at least one of a user identifier, a user first name, a user last name, a job title, a physical address, an email address, and information related to a social security number.

8 . The system of claim 1 , wherein,

the subset of identity data comprises one or more of login information, one or more security questions, respective answers to each of the one or more security questions, and additional user data; and

wherein the additional user data comprises at least one of a user identifier, a user first name, a user last name, a job title, a physical address, an email address, and information related to a social security number.

9 . The system of claim 1 , wherein,

the one or more hardware processors are configured by machine-readable instructions to periodically sync the identity cache with the identity system via the orchestrating agent; and

the identity system comprises a cloud-based identity system.

10 . The system of claim 9 , wherein the orchestrating agent comprises at least one of:

a standard identity protocol and multi-factor authentication (MFA), wherein the standard identity protocol comprising at least one of OpenID Connect (OIDC), Security Assertion Markup Language (SAML), and WebAuthn.;

a multi-factor authentication (MFA); and

a combination thereof.

11 . A method for controlling access to an application, comprising:

requesting to access the application, wherein the application is associated with an identity system;

determining a status of the identity system, the status comprising one of an available status and an unavailable status, and when the status comprises the unavailable status,

transmitting a request for additional information,

receiving the additional information, and

verifying the additional information by referencing an identity cache associated with the identity system;

authenticating a user to access the application when at least one of:

the status comprises the available status, and

the additional information has been verified;

in response to authenticating the user at the application, sending a communication from the application to the user, granting the user access to the application; and

storing a subset of at least one of identity metadata and identity data associated with a plurality of users, including at least the user, to the identity cache, wherein the identity cache is at least one of electronically, logistically, logically, and communicatively coupled to the identity system and an orchestrating agent.

12 . The method of claim 11 , wherein,

requesting to access the application comprises receiving the request at an intermediary prior to determining a status of the identity system;

determining a status of the identity provider comprises using the intermediary to determine the status of the identity system; and

when the status comprises the available status, authenticating the user comprises:

receiving at least some identity data at the identity system from the user,

authenticating the user at the identity system, based at least in part on the at least some identity data, and

receiving a user authentication confirmation at the intermediary.

13 . The method of claim 12 , wherein,

verifying the additional information by referencing an identity cache comprises using the intermediary to reference the identity cache associated with the identity system;

authenticating the user to access the application comprises creating a token at the intermediary;

wherein the token is created based on one of:

receiving the user authentication confirmation at the intermediary; and

using the intermediary to reference the identity cache associated with the identity system; and

in response to authenticating the user at the application, the method further comprises creating a user session with the application.

14 . The method of claim 13 , wherein the at least some identity data comprises at least one of a user identifier, a username, and a password, and wherein the identity system creates a first identity session based at least in part on authenticating the user at the identity system.

15 . The method of claim 14 , wherein prior to creating the token at the intermediary, the method comprises:

providing the intermediary with information pertaining to the first identity session; and

creating, at the intermediary, a second identity session, wherein the second identity session is created in response to the first identity session.

16 . The method of claim 11 , wherein transmitting the request for additional information comprises one or more of:

requesting at least some identity data from the user, the at least some identity data including at least a username and password;

requesting answers to one or more security questions; and

requesting additional identity data from the user, wherein the additional identity data comprises at least one of a user identifier, a user first name, a user last name, a job title, a physical address, an email address, and information related to a social security number.

17 . The method of claim 11 , wherein,

the identity cache stores the subset of identity data;

the subset of identity data comprises one or more of login information, one or more security questions, respective answers to each of the one or more security questions, and additional user data;

the additional user data comprises at least one of a user identifier, a user first name, a user last name, a job title, a physical address, an email address, and information related to a social security number;

the identity cache is periodically synced with the identity system via an intermediary;

the identity system comprises a cloud-based identity system; and

the orchestrating agent comprises at least one of:

a standard identity protocol,

multi-factor authentication (MFA), and

wherein the standard identity protocol comprising at least one of OpenID Connect (OIDC), Security Assertion Markup Language (SAML), and WebAuthn,

a multi-factor authentication (MFA), and

a combination thereof.

18 . A non-transient computer-readable storage medium having instructions embodied thereon, the instructions being executable by one or more processors to perform a method for controlling access to an application, the method comprising:

requesting to access the application, wherein the application is associated with an identity system;

determining a status of the identity system, the status comprising one of an available status and an unavailable status, and when the status comprises the unavailable status,

transmitting a request for additional information,

receiving the additional information, and

verifying the additional information by referencing an identity cache associated with the identity system;

authenticating a user to access the application when at least one of:

the status comprises the available status, and

the additional information has been verified;

in response to authenticating the user at the application, sending a communication from the application to the user, granting the user access to the application; and

storing a subset of at least one of identity metadata and identity data associated with a plurality of users, including at least the user, to the identity cache, wherein the identity cache is at least one of electronically, logistically, logically, and communicatively coupled to the identity system and an orchestrating agent.