danielcweeks commented on PR #10314:
URL: https://github.com/apache/iceberg/pull/10314#issuecomment-2206897363

   @adutra 
   
   > An RFC cannot modify another one's structs without officially superseding 
it. 
   > . . . RFC 8693 as a general rewrite of RFC 6749 section 5.1
   
   I'm not suggesting that this is a general rewrite, but was more interpreting 
that RFC 8693 as an extension that can apply to any access_token grant type 
response.
   
   > . . .  in the scope of a token exchange grant only.
   
   I think this is the best argument and I agree it makes any argument for 
`issued_token_type` for other grant flows to be weak.
   
   > And anyways, that's how all public OAuth 2.0 servers interpret it: none of 
them include the field issued_token_type in a client_credentials grant 
response, even if they support RFC 8693.
   
   Maybe you misinterpreted my message, but I actually support adding this.  I 
couldn't find any examples and I also understand that RFC 8693 isn't widely 
adopted, so we may run into a number of issues with existing implementations 
out there.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org

Reply via email to