Frequently Asked Questions

1. My login does not work / I'm prompted with Password:

   • This is probably due to your Access Token being too long. Access Tokens that exceed a length of 1023 characters cannot be processed by ssh. To find out about the length of your Access Token, run:

   oidc-token | wc -c

2. oidc-agent seems to hang.

   • This is due to a bug in libcjson, and should not appear any longer. It was fixed in oidc-agent 4.1.0-4 (and 4.1.0-5 for ubuntu 20).
   • Contact oidc-agent-contact@lists.kit.edu

3. I cannot run mccli after installing it via pip (or pip3).

   • This may be due to $HOME/.local/bin not being in your $PATH.
   • Try export PATH=$PATH:$HOME/.local/bin to fix it.

4. After running first time I get: error: Could not infer motley_cue endpoint from command

   • Try updating mccli with: pip install -U mccli
   • Try adding --mc-endpoint https://<hostname>:8443 to the mccli command
   • Try adding --mc-endpoint http://<hostname>:8080 to the mccli command
   • Ask a service administrator whether motley_cue runs on a non-standard port

5. I get an error that I am not authorised: error: Failed on get_status: [HTTP 403] "Forbidden: you are not authorised to access this service"

   • Check if your token issuer is supported on the service:

     mccli --oidc <oidc-agent account name> info <hostname>

   • In the command output, check that the issuer URL appears in the list of supported OPs.

   • Look at the information in the section: Authorisation on service for provided token issuer (OP).

     • If the authorisation is VO-based, make sure you are a member of an authorised VO: the section Information retrieved from userinfo endpoint in the output of the command above.
     • In the case of individual user authorisation, contact the service administrator.