On Mon, Jun 3, 2019 at 1:07 PM Hasanthi Purnima Dissanayake < hasan...@wso2.com> wrote:
> Hi Johann, > > The OAuth2 scopes implementation in IS doesn't support providing a human >> readable description that can be shown in to the end-user when providing >> consent. > > > The OAuth2 scopes already have a description, but the internationalization > is not supported. I think this is needed for registered scopes only, not > the custom scopes > What do we mean by custom scopes here? Also does this mean all scopes need to be pre-registered at the scope endpoint? > > +1 for the improvement. > > Thanks, > Hasanthi > > On Mon, Jun 3, 2019 at 12:23 PM Johann Nallathamby <joh...@wso2.com> > wrote: > >> The OAuth2 scopes implementation in IS doesn't support providing a human >> readable description that can be shown in to the end-user when providing >> consent. Just showing the scope names doesn't help the end-user to decide >> whether to grant the scope or not. >> >> The description should also support internationalization as in challenge >> questions. >> >> >> [1] https://github.com/wso2/product-is/issues/5354 >> >> Thanks & Regards, >> Johann. >> >> -- >> *Johann Dilantha Nallathamby* | Associate Director/Solutions Architect | >> WSO2 Inc. >> (m) +94 (77) 7776950 | (w) +94 (11) 2145345 | (e) joh...@wso2.com >> [image: Signature.jpg] >> > > > -- > > Hasanthi Dissanayake | Senior Software Engineer | WSO2 Inc. > (m) +94718407133 | (w) +94112145345 | Email: hasan...@wso2.com > > -- Farasath Ahamed Associate Technical Lead, WSO2 Inc.: http://wso2.com Mobile: +94777603866 Blog: https://farasath.blogspot.com / https://medium.com/@farasath Twitter: @farazath619 <https://twitter.com/farazath619> <http://wso2.com/signature>
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
