n Parad
>>
>> Founder, CTO
>> Secure your user data with IAM authorization as a service. Implement
>> Authress <https://authress.io/>.
>>
>>
>> On Mon, Aug 9, 2021 at 10:44 PM Kevat Shah wrote:
>>
>>> @wpa...@rhosys.ch - Using forgot pas
thress <https://authress.io/>.
>
>
> On Mon, Aug 9, 2021 at 10:15 PM Kevat Shah wrote:
>
>> How would that work? Would we need to work with W3C to ensure conformity
>> of standards?
>>
>> On Mon, Aug 9, 2021, 4:11 PM wrote:
>>
>>> Although th
ork efforts around standardizing password reset
> endpoint discovery, password complexity schemas, etc.
> --
>
> *From:* Kevat Shah
> *Sent:* Monday, August 9, 2021 16:03
> *To:* Tim Cappalli
> *Cc:* oauth@ietf.org
> *Subject:* Re: [OAUTH-WG] Specifications f
lli
wrote:
> I believe this topic would be more W3C scope, not IETF.
>
> tim
> --
> *From:* OAuth on behalf of Kevat Shah <
> kevats...@gmail.com>
> *Sent:* Sunday, August 8, 2021 16:37
> *To:* oauth@ietf.org
> *Subject:* [OAUTH-WG] Spe
I propose that we expand upon specific functionality provided by Identity
Providers (IdPs) and tasks handled by them.
To start with, there should be clear specifications for various
functionalities that IdPs provide such as:
- Email verification on registration
- Specifications regarding "forgot
