[WG-eGov] Moving government toward shared identity management - Notices from 18F

[Angela Rey]

Government launches login.gov to simplify access to public services
In early April, the U.S. Digital Service and 18F launched login.gov, a single sign-on solution for government websites that will enable citizens to access public services across agencies with the same username and password.

https://18f.gsa.gov/2017/08/22/government-launches-login-gov/

GSA adopts 18F Federalist platform to transition federal identity guides Into digital playbooks
The General Services Administration has developed digital versions of its Federal Identity, Credential and Access Management Roadmap and associated implementation guidance and put them online with the adoption of 18F’s Federalist platform.

http://www.executivegov.com/2017/08/gsa-adopts-18f-federalist-platform-to-transition-federal-identity-guides-into-digital-playbooks/

[Colin Wallis]

Many thanks for these news bits Angela.

Login.gov is late into the centralised identity management play vs many other country reps on this list, but there is always something new to learn in terms of approach to adoption and roll out..

And in this case, the fact that login.gov has a recent (800-63-3 compliant) SAML flow alongside an OIDC one, means that folks here and in Kantara's Federated Interop WG will be interested to see how this new kid on the block goes.

It could be a candidate for a future meeting's 'special guest' cameo.. ;-).

Same for the digital playbooks. A clever idea! 

Cheers

Colin  

Executive Director

Cell: +44 (0)7490 266 778

Kantara Initiative Inc.

_______________________________________________
WG-eGov mailing list
WG-...@kantarainitiative.org
http://kantarainitiative.org/mailman/listinfo/wg-egov

[John Bradley]

Looking at the docs, I don’t see a SAML profile.  There is a SP sample app that uses a static config file to talk to the login.gov IdP.  

This seems focused on using SAML and OIDC for SSO from a single IdP rather than some of the more federated use cases.

That is fine,  but not the only use case that needs a profile. 

I also don’t see any reference to SP-800-63-C FAL.   That may be because as a password based system login.gov is focused on FAL1.

Any additional info would be appreciated.

John B.

[Colin Wallis]

Folks

My apologies on not positioning login.gov's compliance correctly.  I'm getting a bit ahead of myself there.. :-).

That's in the same vein as the 'profile' comment ... it's the desired direction of travel for a future state rather than the current state.

Cheers

Colin

 

 

Executive Director

Cell: +44 (0)7490 266 778

Kantara Initiative Inc.

On Mon, Aug 28, 2017 at 8:29 PM, Grassi, Paul A. (Fed) <paul....@nist.gov> wrote:

And login isn't 63-3 compliant either. Hence the missing elements.