Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
sdods auth capture -p rwa-bank -e local -u admin --index 3✖ USER_POOL_EXHAUSTED: Role "admin" has 2 user(s); index 3 does not exist.The CSV has six rows and the admin I want is on the fourth one, so index 3 by my counting. Where does "2 user(s)" come from?
Accepted answer
--index is the position within the role, not the row number in the file. Filter to the admins, number them from zero: two admins means index 0 and index 1, and the fourth row of the file is one of those two.
It is the same number that names the cached state, which is the easiest way to see it:
sdods auth list -p rwa-bank -e localIf you want all of them rather than one, skip the counting:
sdods auth capture -p rwa-bank -e local -u admin --allOne more thing that had us puzzled for a while: capture skips a user whose cached state is still fresh, so re-running it can look like it did nothing. --force recaptures regardless, and auth.maxAgeMinutes in the project yaml is what "fresh" means.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.