FIRST Community Developers/Discussion/FRC Event API/FRCAPI 401 Unauthorized - Username Not Found/List of Posts
 
Forum Topic - FRCAPI 401 Unauthorized - Username Not Found: (16 Items)
   
Update
Thomas Clark (WPI)(deleted)
03/03/2015 6:45 PM
post4301
FRCAPI 401 Unauthorized - Username Not Found   
I get a 401 response code with "Username Not Found" with every request I make, both on the test and the production 
server.

I'm providing an Authorization field, which I generated like this:

    echo Basic $(echo -n 'ThomasClark:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' | base64)

And this is what my code looks like:

    try:
        req = urllib2.Request('https://frc-staging-api.usfirst.org/api/v1.0/2014')
        req.add_header('Authorization', authorization_token)
        req.add_header('Accept', 'application/json')
        print json.load(urllib2.urlopen(req))
    except urllib2.HTTPError, e:
        raise Exception('{} {} - {}'.format(e.code, e.msg, e.fp.read()))

Any ideas?
Kyle Dunlop(deleted)
03/03/2015 9:22 PM
post4302
Re: FRCAPI 401 Unauthorized - Username Not Found   
I am having the same issue.
Jon Stratis (2177)(deleted)
03/03/2015 10:12 PM
post4303
Re: FRCAPI 401 Unauthorized - Username Not Found   
My solution (in Java) is working fine:

            String clearAuth = "Username:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx";
            String encodedAuth = new String(Base64.encodeBase64(clearAuth.getBytes()));

            connection.setRequestProperty  ("Authorization", "Basic " + encodedAuth);

From what you posted, it looks like you need to prepend "Basic " to the encoded authorization token before attaching it 
to the request.
Thomas Clark (WPI)(deleted)
03/03/2015 11:35 PM
post4310
Re: FRCAPI 401 Unauthorized - Username Not Found   
I'm not sure that's true.  There's a separate response for invalid authorization ("Unable To Determine Authorization 
Token").  According to the docs, the "Username Not Found" response happens when the format is correct but the username 
isn't on file.

I'm not sure about Kyle, but you'll also notice in my original post that I did include "Basic ", so that's not the 
problem.
  Post Deleted
Phil Lopreiato (The Blue Alliance)
03/03/2015 11:30 PM
post4309
Re: FRCAPI 401 Unauthorized - Username Not Found   
The following bash alias works for me

alias frc-api="curl --header \"Authorization: Basic $(echo -n 'user:token ' | base64)\""
Alan Fisher(deleted)
03/05/2015 1:09 AM
post4316
Re: FRCAPI 401 Unauthorized - Username Not Found   
I just tested the username / token emailed to me with this, and it returns "Username Not Found".
-Alan
Alan Fisher(deleted)
03/04/2015 12:02 AM
post4311
Re: FRCAPI 401 Unauthorized - Username Not Found   
I'm also having the same issue. I received an email with my API key on 2015/03/02. I'm fairly certain I've encoded the 
username / key combination correctly.
Duane Beck(deleted)
03/05/2015 9:10 PM
post4326
Re: FRCAPI 401 Unauthorized - Username Not Found   
My authentication code was working yesterday, and today I am getting 401 Unauthorized.  I have not changed the code 
which generates the authentication string in over a week.
Alex Herreid (FIRST)
03/05/2015 9:13 PM
post4327
Re: FRCAPI 401 Unauthorized - Username Not Found   
Hi Duane, please contact me directly for support (the message you are receiving should have said this as well). Your 
token was blocked for excessive use.
Justin Kleiber (624)(deleted)
03/06/2015 4:45 AM
post4330
Re: FRCAPI 401 Unauthorized - Username Not Found   
When I try to use the API with my new key in PHP I get the following string return:

string 'Username Not Found' (length=18)

This is how I encode my Authorization Token:

$auth = "Authorization: Basic " . base64_encode(Username:XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX);

Clearly the encoding is working because the Docs say that whenever this error is returned that the api 'finds' a decoded
 username, but that that username is not actually registered.

Is it possible that anyone recently added to the API token list may not be added on the API side yet?

Thanks
Thomas Clark (WPI)(deleted)
03/06/2015 4:51 PM
post4331
Re: FRCAPI 401 Unauthorized - Username Not Found   
It seems unlikely that it has to do with being added recently.  I got my token four days ago, and it still doesn't work.
  I'm just speculating, though - it's impossible to tell until someone from FIRST speaks up.
Justin Kleiber (624)(deleted)
03/06/2015 11:04 PM
post4333
Re: FRCAPI 401 Unauthorized - Username Not Found   
> It seems unlikely that it has to do with being added recently.  I got my token
>  four days ago, and it still doesn't work.  I'm just speculating, though - 
> it's impossible to tell until someone from FIRST speaks up.

I'm not sure either, but I also got my token 4 days ago.

> Are you using the staging API (frc-staging-api.usfirst.org) or the production 
> one? (frc-api.usfirst.org)

Regardless of which one I use, I get the same error.
Nicholas McCurry(deleted)
03/06/2015 5:49 PM
post4332
Re: FRCAPI 401 Unauthorized - Username Not Found   
Are you using the staging API (frc-staging-api.usfirst.org) or the production one? (frc-api.usfirst.org)
Duane Beck(deleted)
03/10/2015 3:00 PM
post4335
Re: FRCAPI 401 Unauthorized - Username Not Found   
I've sent a direct email to you.
Alex Herreid (FIRST)
03/10/2015 4:11 PM
post4336
Re: FRCAPI 401 Unauthorized - Username Not Found   
Hi everyone,
It appears that certain usernames we receive from TeamForge come with a carriage return character added to the end of 
them- hence not being able to find that username on an API request. If you are having trouble with your username, please
 send me a direct email and we will double check it.
I think everyone who commented on this thread we have already replied to directly via email- so please check that first.

Thanks

Return