From e101340f1483d9d53951685abdc146e24df7001e Mon Sep 17 00:00:00 2001 From: "Yann Esposito (Yogsototh)" Date: Wed, 4 May 2022 15:29:25 +0200 Subject: [PATCH] notes/cisco_org_level_entities.org --- notes/cisco_org_level_entities.org | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/notes/cisco_org_level_entities.org b/notes/cisco_org_level_entities.org index 075bf6e7..9e07cb84 100644 --- a/notes/cisco_org_level_entities.org +++ b/notes/cisco_org_level_entities.org @@ -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-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 -could in the worst case scenario last for a few weeks. +The time during which two passwords could be accepted could last up to a few weeks. * Tasks - [ ] 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. - 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. - [ ] OPTIONAL Support client-secret reset