Once the necessary components are deployed to the API Portal beta site, validate the following test cases:
- [ ] User with an unconfirmed email address is prompted to confirm their email before they can create a client
- Failed: See T264110
- [ ] User with a confirmed email address can create a client
- Failed: See T264215
- [ ] When creating an owner-only client, the form requires a client name, description, and terms agreement.
- [ ] After creating an owner-only client, a dialog appears with the client ID, secret, and token.
- [ ] When creating a non-owner-only client, the form requires a client name, description, return URL, confidential status, and terms agreement.
- [ ] After creating a non-owner-only client, a dialog appears with the client ID and secret.
- [x] Existing OAuth 2.0 clients appear in the client list with their name, created date, and status
- [x] Existing OAuth 1.0 clients do not appear in the client list
- [ ] The client details view shows the client ID
- Failed: See T264238
- [ ] For an owner-only client, the client secret and token can be reset using the reset option
- Failed: See T264240
- [ ] For a non-owner-only client, the client secret can be reset using the reset option
- Failed: See T264240
- [ ] Changes in client status are reflected in the Portal
- [ ] Client credentials created via the Portal work with the Gateway
### Issues identified
* {T264110}
* {T264199}
* {T264201}
* {T264202}
* {T264215}
* {T264238}
* {T264240}