Settings and activity
37 results found
-
1 voteMorten Lied Johansen shared this idea ·
-
3 votesMorten Lied Johansen supported this idea ·
-
5 votesMorten Lied Johansen supported this idea ·
-
15 votesMorten Lied Johansen supported this idea ·
-
7 votesMorten Lied Johansen supported this idea ·
-
2 votesMorten Lied Johansen supported this idea ·
-
6 votes
An error occurred while saving the comment Morten Lied Johansen supported this idea · -
34 votesMorten Lied Johansen supported this idea ·
-
3 votesMorten Lied Johansen supported this idea ·
-
2 votesMorten Lied Johansen supported this idea ·
-
4 votesMorten Lied Johansen supported this idea ·
-
8 votesMorten Lied Johansen supported this idea ·
-
21 votesMorten Lied Johansen supported this idea ·
-
25 votesMorten Lied Johansen supported this idea ·
-
3 votesMorten Lied Johansen supported this idea ·
-
3 votesMorten Lied Johansen supported this idea ·
-
10 votesMorten Lied Johansen supported this idea ·
-
16 votesMorten Lied Johansen supported this idea ·
-
2 votesMorten Lied Johansen supported this idea ·
-
3 votesMorten Lied Johansen supported this idea ·
To work around this limitation, we have built tooling that provisions new service users for applications when credentials needs to be rotated, so that we can switch the applications over to the new service user before deleting the old one.
This results in effectively 2-3 service users per application at any given time.
This has resulted in us hitting the limit to the number of service users a service can have several times, and as our application portfolio continues to grow, the problem continues.
Being able to gracefully replace credentials would allow for a single service user per application.