Terminology for OAuth flows is incorrect

[cbryanreapit]

Developers are required to select the auth flow that their application will use as part of registration process:

The terminology for these flows isn't right. OAuth is a well known standard for managing auth so urge that we standardise our UI to present recognisable flow names

User session should be authorization code / Reapit Connect
Client secret should be client credentials

Similar but less important, I think it wouldn't hurt to get the 'scopes' terminology in here. We use 'permissions' at present, which is more user friendly, but scopes is an OAuth concept that indicates to the developer that their bearer token will be responsible for delivering their access via scopes.

See mock up:

Please can we hyperlink the 'Reapit Connect' to https://foundations-documentation.reapit.cloud/api/reapit-connect

[duong-se]

Similar but less important, I think it wouldn't hurt to get the 'scopes' terminology in here. We use 'permissions' at present, which is more user friendly, but scopes is an OAuth concept that indicates to the developer that their bearer token will be responsible for delivering their access via scopes.

So will we include these edit in this issue also?

[HollyJoyPhillips]

@tanphamhaiduong Regarding your comment above, it's a good point. I'll have a review and come back to you. Let's leave it for the moment as we will need to go back to this section to update the URL for the docs so we can review it then.

Also, as discussed at StandUp, please can you also update the terminology for the app modal when 'Client Credentials' is selected. It should say 'Show Client Credentials' not 'Show Client Secret'. This is only visible in the Developers portal, thank you.

[duong-se]

@HollyJoyPhillips Yes, I will do that.

[HollyJoyPhillips]

@tanphamhaiduong Thanks, looks good. Can you add the hyperlink on 'Reapit Connect'?