OIDF-automation

### Imported from AB/Connect bitbucket - Original Commenter: mbj I’m mostly prone to let OAuth describe itself, but a few sentences of overview would be OK. Aaron Parecki noted on...

### Imported from AB/Connect bitbucket - Original Commenter: KristinaYasuda we could add a basics of OAuth 2.0 section in the whitepaper and in the OpenID4VC specs simply add an implementation...

### Imported from AB/Connect bitbucket - Original Commenter: pedro-felix My current opinions on this subject: * Scopes are the original mechanism to express authorization requirements on OAuth 2.0, while RAR...

### Imported from AB/Connect bitbucket - Original Commenter: KristinaYasuda I am not comfortable removing `scope` option. To reiterate on what I have already put in PR #520. Mandating RAR increases...

### Imported from AB/Connect bitbucket - Original Commenter: authlete-taka > \(personally I preferred the offer string to be the credential\_supported id and not the scope\) Really. Adding `scope` would have...

### Imported from AB/Connect bitbucket - Original Commenter: KristinaYasuda I think we can still add `id` - Issue #1922 has not been resolved.

### Imported from AB/Connect bitbucket - Original Commenter: KristinaYasuda > I don’t buy the argument scopes are needed to keep things simple. authorization details might be more verbose but for...

### Imported from AB/Connect bitbucket - Original Commenter: KristinaYasuda noting number of recent requirements around server-to-server \(organization to organization\) issuance/presentation flows using client\_credentials grant, where scopes are used to communicate...