Administration portal for simulated single sign-on

A method for securely managing security policy data used to provide users access to third-party applications without revealing credentials to the users, the method comprising:

• storing security policy data, the security policy data comprising, for each user, a list of third-party applications to which the user may request access and corresponding sign-on credentials for accessing each of the third-party applications;
• receiving a selection of a first deployment to configure, the first deployment corresponding to a first third-party application and a first network address for a first sign-on page of the first third-party application;
• receiving first sign-on credentials for the first deployment, wherein the first sign-on credentials provide access to the first third-party application via the first sign-on page;
• receiving a selection of a second deployment to configure, the second deployment corresponding to a second third-party application and a second network address for a second sign-on page of the second third-party application;
• receiving second sign-on credentials for the second deployment, wherein the second sign-on credentials provide access to the second third-party application via the second sign-on page;
• in response to an attempt to associate the first sign-on credentials with a first user, sending a first request to a permission server to confirm that the first user is permitted access to the first third-party application, wherein the permission server is configured to store permission data comprising a list of third-party applications to which the users are currently permitted access;
• receiving a first response to the first request, wherein the first response comprises a confirmation or denial of permission to access the first third-party application by the first user;
• in response to the first response comprising a confirmation of permission to access the first third-party application by the first user, associating the first user with the first sign-on credentials;
• in response to an attempt to associate the second sign-on credentials with a second user, sending a second request to the permission server to confirm that the second user is permitted access to the second third-party application;
• receiving a second response to the second request, wherein the second response comprises a confirmation or denial of permission to access the second third-party application by the second user;
• in response to the second response comprising a confirmation of permission to access the second third-party application by the second user, associating the second user with the second sign-on credentials;
• and
• automatically updating the stored security policy data, based on the association of the first sign-on credentials with the first user and the association of the second sign-on credentials with the second user, such that the stored security policy data comprises:
• a first entry for the first deployment, the first entry comprising an identifier of the first user, the first sign-on credentials, and the first network address;
• and
• a second entry for the second deployment, the second entry comprising an identifier of the second user, the second sign-on credentials, and the second network address.

A device for securely managing security policy data used to provide users access to third-party applications without revealing credentials to the users, the device comprising:

• a memory configured to store security policy data, the security policy data comprising, for each user, a list of third-party applications to which the user may request access and corresponding sign-on credentials for accessing each of the third-party applications;
• and
• a hardware processor communicatively coupled to the memory and a network, the processor configured to:
• receive a selection of a first deployment to configure, the first deployment corresponding to a first third-party application and a first network address for a first sign-on page of the first third-party application;
• receive first sign-on credentials for the first deployment, wherein the first sign-on credentials provide access to the first third-party application via the first sign-on page;
• receive a selection of a second deployment to configure, the second deployment corresponding to a second third-party application and a second network address for a second sign-on page of the second third-party application;
• receive second sign-on credentials for the second deployment, wherein the second sign-on credentials provide access to the second third-party application via the second sign-on page;
• in response to an attempt to associate the first sign-on credentials with a first user, send a first request to a permission server to confirm that the first user is permitted access to the first third-party application, wherein the permission server is configured to store permission data comprising a list of third-party applications to which the users are currently permitted access;
• receive a first response to the first request, wherein the first response comprises a confirmation or denial of permission to access the first third-party application by the first user;
• in response to the first response comprising a confirmation of permission to access the first third-party application by the first user, associate the first user with the first sign-on credentials;
• in response to an attempt to associate the second sign-on credentials with a second user, send a second request to the permission server to confirm that the second user is permitted access to the second third-party application;
• receive a second response to the second request from the permission server, wherein the second response comprises a confirmation or denial of permission to access the second third-party application by the second user;
• in response to the second response comprising a confirmation of permission to access the second third-party application by the second user, associate the second user with the second sign-on credentials;
• and
• automatically update the security policy data, based on the association of the first sign-on credentials with the first user and the association of the second sign-on credentials with the second user, such that the security policy data comprises:
• a first entry for the first deployment, the first entry comprising an identifier of the first user, the first sign-on credentials, and the first network address;
• and
• a second entry for the second deployment, the second entry comprising an identifier of the second user, the second sign-on credentials, and the second network address.