GSA Auth Implementation - Mural

[JJediny]

Hello,

As an owner or developer of a GSA Application, GSA IT is informing you that we are ready to proceed with the replacement of Secure Auth with the new multi-factor authentication (MFA) tool called GSA Auth.

GSA Auth will be used to ensure security protocols for your application login needs. This change will impact the method employees and contractors access applications that require MFA.

On this call we will:

Overview GSA Auth Processes/Set Expectations

Validate Mural and New Relic Data (see link below)

Confirm Readiness to Proceed

GSA Auth New Application Intake Form_App Name

**Please review/update the form via the link and have your Lead Technical POC submit prior to the session. Select Continue to record responses in the form. The following data is mandatory to begin SAML migration/implementation:

Single sign-on URL - This URL is required and serves as the default Assertion Consumer Services (ACS) URL value for the Service Provider (SP). This URL is always used for Identity Provider (IdP) initiated sign-on requests.

Audience URI (SP Entity ID) - The intended audience of the SAML assertion. This is usually the Entity ID of your application.

Metadata Files-All Environments (XML format-filename should follow the app name - Ex. GSA IDTB OIDC (app name) GSA_IDTB_OIDC.xml)

GSA Auth Engineer Lead: Nathan Kim

This invite may be forwarded to any technical POCs that may have been inadvertently missed in scheduling this invite.

For more background information, please visit the GSA Auth informational Google site at https://sites.google.com/gsa.gov/gsauth/home. (See Onboarding)

Technical teams and UAT testers will need to have enrolled into the GSA Auth Preprod environment in order to access migrated applications. For instructions on setting up a GSA Auth account, please follow these instructions.

[JJediny]

8/13

Lenia Cash will notify users

• [x] DRAFT email
• [x] Email user list about timing

[JJediny]

Tested and Completed 8/16