notes/cisco_org_level_entities.org
This commit is contained in:
parent
7a5284dc36
commit
e101340f14
1 changed files with 3 additions and 4 deletions
|
@ -49,13 +49,12 @@ So it means adding the following optional fields to the client object:
|
||||||
- ~old-password~: the old password on password change
|
- ~old-password~: the old password on password change
|
||||||
- ~old-password-valid-until~: the date after which the old password will be rejected.
|
- ~old-password-valid-until~: the date after which the old password will be rejected.
|
||||||
|
|
||||||
The time during which two passwords could be accepted is probably value that
|
The time during which two passwords could be accepted could last up to a few weeks.
|
||||||
could in the worst case scenario last for a few weeks.
|
|
||||||
|
|
||||||
* Tasks
|
* Tasks
|
||||||
- [ ] Support org-level client:
|
- [ ] Support org-level client:
|
||||||
1. add a ~org-level?~ boolean field. If this field is true then the
|
1. add an ~org-level?~ boolean field. If this field is true then the
|
||||||
client must not have any ~owner-id~ field.
|
client must not have any ~owner-id~ field.
|
||||||
2. org-level clients should be visible to all admins, for read and search
|
2. org-level clients should be visible to all admins, for reading and searching
|
||||||
3. we should provide a new route to promote normal clients to org-level clients.
|
3. we should provide a new route to promote normal clients to org-level clients.
|
||||||
- [ ] OPTIONAL Support client-secret reset
|
- [ ] OPTIONAL Support client-secret reset
|
||||||
|
|
Loading…
Reference in a new issue