Login via oidc-ssh fails: "Internal server error" reported by `motley_cue` when trying to deploy user
It seems motley_cue
now reports an internal server error when one attempts to deploy a user who is already deployed:
$ curl -H "Authorization: Bearer `oidc-token helmholtz`" -X GET https://c4p-login.gridka.de/user/get_status
{"state":"deployed","message":"username o_freyermuth"}%
$ curl -H "Authorization: Bearer `oidc-token helmholtz`" -X GET https://c4p-login.gridka.de/user/deploy
Internal Server Error
A nice side-effect of not using the status endpoint was that the username returned by deploy
could easily be parsed from the JSON response, while for the get_status
endpoint, additional messy string manipulation is required.
@manuel.giffels Do you see any errors related to such an attempt in the server logs?
I tried to learn from the code what changed, but got lost somewhere between motley_cue
and the feudalAdapter
. It seems a state machine should be triggered and it may be regarded as a bug that Internal server error
is returned when the target state is deployed
and the user is already deployed
, so instead of working around this in oidc-ssh
, maybe we can restore the working behaviour in motley_cue
;-).