Yes there should be corresponding client_secret_SAML and private_key_SAML. Those parameters were taken from Connect which is more JWT focused so I didn't put in the SAML options for token endpoint authentication, though they would be valid.
There is probably some profiling that needs to be done for the client_secret_SAML to define how the client secret is used to hmac the SAML assertion. You might want to just skip that and only do private_key_SAML which is more strait-forward with a asymmetric signature. John B. On 2013-04-24, at 5:17 PM, Phil Hunt <phil.h...@oracle.com> wrote: > For parameters to token_endpoint_auth_method, the spec has defined > "client_secret_jwt" and "private_key_jwt". Shouldn't there be similar options > of SAML? > > Shouldn't there be an extension point for other methods? > > Phil > > @independentid > www.independentid.com > phil.h...@oracle.com > > > > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
