[Openid-specs-ab] FICAM LoA for Connect

John Bradley ve7jtb at ve7jtb.com
Mon May 21 18:09:19 UTC 2012

I would anticipate a profile going to LoA 3 (non-crypto) using the code flow and asymmetric signatures.

Because Connect/JWT/JOSE are not final specs there probably won't be a profile specifically for Connect in the very short term.

I might anticipate a more general profile for doing authentication with OAuth that Connect happens to conform to as a first step.

If you want, I could talk to them about what might hypotheticly be in such a profile.

John B.

On 2012-05-21, at 1:06 PM, Justin Richer wrote:

> I've been asked by a few folks here and in my company's sponsoring organizations about exactly how OpenID Connect would fit into a FICAM profile, especially at LoA2 and LoA3 (non-crypto). I do realize that in order for there to be a real profile, someone from the gov't needs to sit down and write one and have it ratified. But since it's my understanding that Connect is being built in order to support higher LoA, what do the members in this community anticipate being part of such a profile?
> -- Justin
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4937 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20120521/9e59b77e/attachment-0001.p7s>

More information about the Openid-specs-ab mailing list