Torsten Lodderstedt
OAuth 2
Published in
1 min readJun 30, 2019

--

As I stated, use a public client (i.e. w/o a secret). That’s the same recommendation as for native apps (https://tools.ietf.org/html/bcp212). Clearly, the AS must take this into consideration when determining the level of trust it puts into the client‘s identity.

And do not forget to use PKCE in order to detect code injection attempts. Please take a look into https://tools.ietf.org/html/draft-ietf-oauth-security-topics-12#section-3.1 for the full set of security guidelines.

--

--

OAuth 2
OAuth 2

Published in OAuth 2

Learnings, Patterns and Ideas around use of OAuth 2.0

Torsten Lodderstedt
Torsten Lodderstedt

Written by Torsten Lodderstedt

Torsten is CTO@yes.com, software architect with strong security interest, identity nerd, contributor to OAuth, OpenID, Open Banking & Electronic Signatures