Thanks, I’ll take a look. One question, though: why keep the “id” query parameter? If used, we’re always going to have to do issuer discovery. It may be simpler to just not use that parameter.
Scott From: Pawel Kowalik <[email protected]> Sent: Friday, April 22, 2022 8:21 AM To: Hollenbeck, Scott <[email protected]> Cc: [email protected] Subject: [EXTERNAL] Re: [regext] Feedback to draft-ietf-regext-rdap-openid-12 Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Scott, > [PK] sure, not insisting on dynamic registration. How do you want to proceed > with drafting the text update? > Do you maintain the test somewhere on github or alike where I could chip in > a proposal? [SAH] Please send proposed text to the list. I'm still doing this draft the old school way. 😉 [PK] Attached the patch file with a proposal (I hope it goes through the mailing list). In short, it adds an openidcRemoteConfiguration object to the /help resource, which indicates support for Issuer Identifier of an OP and the list of OPs. /session/login end point now accepts either "id" or "remote_iss" query parameters. One can also specify both, but at least one must be present. Kind regards Pawel
_______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
