User logins

[BryceStevenWilley]

There are currently 3 problems with EFM logins:

1. the fact that they exist separately from docassemble logins is confusing UX wise. Unfortunately, this will persist for as long as we don't want to make people login to our site, but we still allow them to, and as long as Tyler's system requires logins and everything outside is uses those logins.
2. logins are interview specific: if you are logged in in one interview and restart or go to another interview, you won't be logged in there. This isn't as big of a deal now, with only 1 efiling interview per jurisdiction, but will become a bigger issue when we start to add follow up interviews and status pages and payment method interviews
3. the fact you have to make a EFM account at all. We could make people an account automatically, keeping their password encrypted.

The solution to 2 and 3 is to use a DAStore and either auto make a password for people, or just hang on to the loggedin hash (we already do this, just in the interview session), and store it with encryption across all interviews, which DAStore should do.

Something else that affects this: Tyler has announced they are letting courts use Okta for authentication, rolling out over the next year, using OICD for the backend. I still don't quite understand the flow from a UX persective, but we likely will not be able to auto make people's passwords and log them in. We should still be able to hang on to the hash until it expires in a DAStore.

[BryceStevenWilley]

Going to look into this a lot this month; if Okta is available in IL with ECF (or anywhere we are integrated for that matter), we should get as far as we can with integration.

[nonprofittechy]

Do you mean Okta?