On 6/12/17 12:20 PM, David Waite wrote:
FYI, A few years ago I did a demonstration on OpenID Connect at Cloud
Identity Summit using a collection of bash scripts and command-line
utilities (nc, jq). I used the macOS system command ‘open’ to launch a
browser, and netcat to field the response as a poor man’s HTTP
endpoint. The code for that presentation is at
https://github.com/dwaite/Presentation-Code-OpenID-Connect-Dynamic-Client-Registration
A few options for the user challenge/consent portion of the
authentication are:
- use non-HTML request/response API (around some custom MIME type) to
drive a user agent through the authentication/scope approval/etc
stages of your AS
This is the option I'm interested in. Something simple around 401
challenges, text/plain mime type, and simple stdin processing. I"ll
post what I'm thinking of if its appropriate. A colleague pointed me to
SASL + HTTP [1], but not sure if that's what I'm looking for.
Thanks everybody,
Bill
[1] https://tools.ietf.org/html/draft-nystrom-http-sasl-09
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
