Hi all,
I'm having a similar issue to [this one](https://www.synapse.org/#!SynapseForum:threadId=10828), except that I've never been able to log in. No matter what, I always get the following error:
```
export SYNAPSE_AUTH_TOKEN=''
synapse login -p $SYNAPSE_AUTH_TOKEN
SynapseAuthenticationError: You are not logged in and do not have access to a requested resource.
caused by SynapseHTTPError: 401 Client Error:
Invalid access token
```
(with replace with my actual access token)..
I've tried creating multiple auth tokens and followed the steps from [the link mentioned previously](https://www.synapse.org/#!SynapseForum:threadId=10828) (including messing around with the .synapseConfig file found in `~/.local/lib/python3.10/site-packages/synapseclient`; there is no `.synapseConfig` file in `~/`)
One potential issue: I'm working on a remote cluster, where I don't have sudo permissions. When I `synapse --debug login`, I get a response... so don't think there's a firewall issue? But I don't really know.
Here some anonymized info from the top of `synapse --debug login -p $SYNAPSE_AUTH_TOKEN (not including the full traceback):
```
2024-04-11 14:02:12,249 [client:5827 - DEBUG]: Sending get request to /userProfile
Traceback (most recent call last):
File "~/.local/lib/python3.10/site-packages/synapseclient/client.py", line 5786, in _handle_synapse_http_error
exceptions._raise_for_status(response, verbose=self.debug)
File "~/.local/lib/python3.10/site-packages/synapseclient/core/exceptions.py", line 159, in _raise_for_status
raise SynapseHTTPError(message, response=response)
synapseclient.core.exceptions.SynapseHTTPError: 401 Client Error:
Invalid access token
>>>>>> Request <<<<<<
https://repo-prod.prod.sagebase.org/repo/v1/userProfile GET
>>> Headers: {'User-Agent': 'synapsecommandlineclient synapseclient/4.1.1 python-requests/2.28.1', 'Accept-Encoding': 'gzip, deflate, br', 'Accept': 'applicat
ion/json; charset=UTF-8', 'Connection': 'keep-alive', 'content-type': 'application/json; charset=UTF-8', 'Cookie': 'sessionID=93a06029-f349-42f3-81d3-47f0f65e
fb46', 'Authorization': 'Bearer XXXXX-ACCESS-TOKEN-REMOVED-XXXXX'}
>>> Body: None
>>>>>> Response <<<<<<
>>> Headers: {'Date': 'Thu, 11 Apr 2024 18:02:12 GMT', 'Content-Type': 'application/json;charset=ISO-8859-1', 'Content-Length': '106', 'Connection': 'keep-ali
ve', 'Server': '34 f6e676 27, 1647 57 c616 4796f6 e6 3712 0295. f6 5702 66f657 e6 4602 f657 27 02 3756, 3627 5647e2.', 'X-XSS-Protection': '1;mode=block', 'X-
Content-Type-Options': 'nosniff', 'Access-Control-Allow-Origin': '*', 'WWW-Authenticate': 'Bearer realm="Synapse Repository Services"', 'Vary': 'Accept-Encodi
ng,User-Agent', 'Content-Encoding': 'gzip', 'X-Frame-Options': 'SAMEORIGIN'}
>>> Body: {"concreteType":"org.sagebionetworks.repo.model.ErrorResponse","reason":"Invalid access token"}
```
Any help would be much appreciated!
Created by Alex Vargo ahsv Update: upon logging back into the remote machine, everything was working.
So - not sure what was going wrong, but seems to have been something w/ the configuration of the cluster.
Drop files to upload
Login issue with invalid access token page is loading…