Skip to content Skip to left sidebar Skip to right sidebar Skip to footer

Tag: Okta

Time is ticking to get your FAS ID

GSA recently shared that they will transition to FAS ID for login as part of a system update scheduled for April 14, 2026.

Here’s what to expect:
You will receive a separate email from Okta (sent from no*****@**ta.com or MFA-No-Reply+no*****@*sa.gov) during the week of April 6. This email will include instructions to complete your FAS ID registration before the April 14 transition.(assist.gsa.gov April 6 2026) After you click the activation link, you will:

  • Create a password
  • Set up a security question and answer

Once you complete these steps, your FAS ID credentials will be ready to use on April 14.(ibid)

👉 Please note that the registration link expires after 7 days, so please act promptly.

👉 If you do not receive the email, please check your junk or spam folder.

GSA considers this timeline tentative and will notify you by email if anything changes. (ibid)

Should you have any questions, feel free to give us a call.

We See the Future and it is … Single Sign On

By now you’ve likely heard of Single Sign On (SSO). It’s not exactly new, and it’s currently used by just a few agencies, but it is the wave of the future as agencies move to more cloud-based apps. In fact, 6 U.S. Code § 1523(b)(1)(D), a provision of law governing federal cybersecurity regulations, states that agency heads must “implement a single sign-on trusted identity platform for individuals accessing each public website of the agency that requires user authentication.” This provision was created by GSA working with the Department of Homeland Security. (FedTech, May 24, 2019)

What exactly is SSO? SSO allows a user to sign in one time with one high-strength password and access all that specific user’s authorized applications. With SSO, a user need not memorize a different password for each and every application they access. SSO uses the Security Assertion Markup Language protocol that gives the user the ability to log on once for affiliated but separate websites. According to Tracy David, a cloud client executive at CDW, SSO uses “highly complex encrypted keys, which the end user has no access to view or change.” Ultimately, this makes for a much higher level of security for each agency. (ibid)

At this time, you must log in to each app with a different password. More often than not, passwords across applications are similar (if not the same) and easily remembered. This weakens the security level of the agency as stolen credentials account for roughly 80 percent of breaches. With SSO, you have one complex, single-sign-on password protected with multi-factor authentication.  (ibid)

Many agencies are still using on-premises SSO, which will be more difficult as apps move to the cloud. Insiders believe that the Defense Department’s forthcoming Joint Enterprise Defense Infrastructure cloud contract signals cloud adoption becoming the “norm” in government.

Questions about how this affects your current government contract, or how you might work with the government on SSO Technology? Give us a call at 301-913-5000.