Forum Replies Created
-
Posts
-
The bastion key is only needed when you ssh to your VMs. Invalid token is a separate issue.
Are you using the FABRIC Jupyterhub or tying to install the API on your own system?
If the token is correct then it should work. One quirk of Jupyter notebooks is that if you changed something outside of an open notebook you likely need to force the notebook to re-read the update. I often see this when I update a library (i.e pip install X) or fetch a new token.
Depending on your setup, you will at least need to restart the Jupyter kernel by clicking the button with the arrow that loops in a circle. If you are running this in a custom setup, might need to reload the browser tab that is running the notebook.
Let me know if this solves the problem.
Paul
You can get the token from the portal link that you posted. All you need to do is to click create token then download it. You issue may have been caused by the RENCI power outage the other day. During the power outage tokens could not be created.
Does it work for you today?
This is a known bug. It is caused by communication between FABRIC and CILogon. Occasionally, there is a CIlogon delay that is long enough to trigger a timeout. When this happens your token will be revoked and the next time you submit a request to FABRIC you will get an “invalid token” error.
In the long term we are trying to avoid this timeout so the tokens will not be revoked. In the short term the workaround is to download a new token from the portal. https://portal.fabric-testbed.net/experiments
If you are using our JupyterHub, you will need to logout and and log back in to get a new token.
I just tried to manually set your account to “approved”. Let me know if that worked. If not, I probably need to delete you account and have you start over.
