Persist users who login using api_client param

[sbose78]

1. On login, check if api_client param is present ( as done now ). If the user doesn't exist in the DB, create a record before returning a token.

2. [ not critical now ] Modify Create User API to allow updating the user record with the cluster api url. This change would be needed if the same RHD user now wishes to login to OSiO.

[sbose78]

We could do (1) now and move on. If needed, we could add support for (2) later on.

[sbose78]

@sbryzak This should solve the concern of issuing tokens to users whose record doesn't exist. What do you think?

[sbryzak]

@sbose78 Certainly, this would solve the problem of unrevokable tokens, as we would be able to create a token record if the user has a corresponding identity record.

[xcoulon]

@sbose78 if step 2 is not critical for now and can be addressed later, shouldn't we open a separate issue for it?

[sbose78]

if step 2 is not critical for now and can be addressed later, shouldn't we open a separate issue for it?

Yeah, if it's not solved in a single PR, we could do that.