Field API Login - 401

[Anonymous]

We trying to login using the https://bim360field.autodesk.com/api/login using the required credentials. The username has admin access to the project and Field account. We get "401-Unauthorized credentials" as response for this. What are we missing here?  

[mikako_harada]

Hi Praveen, 

Looks like you are missing "s" in https

URL: https://bim360field.autodesk.com/api/login

For more detail: 

https://fieldofviewblog.wordpress.com/2015/04/08/lab1-hello-field-world/

[Anonymous]

Thanks for the response.

Have tried that too, with 'https'. Still doesnt work. Same response, 401.

[mikako_harada]

Are you based in Europe?  If so, maybe this one? 

https://fieldofviewblog.wordpress.com/2016/08/18/base-url-for-bim-360-field-in-european-countries/

[Anonymous]

No. We are based out of India. And mapped to the US servers.

[mikako_harada]

Do you have many expired accounts?   Such as expired trial accounts?  

https://forums.autodesk.com/t5/bim-360-api-forum/bim-360-api-fails-when-trying-to-connect-to-field/m...

[Anonymous]

No. The account is active. And all the projects the user is admin for are also active.

[mikako_harada]

Praveen,

I understand the account you are accessing through UI right now is active. But since your are saying that you cannot access through API, I'm trying to confirm is if you have ever used other accounts in the past, which you no longer have an access, such as expired trials.  

As discussed in this thread, we had a case where a user had expired accounts, which was preventing for him to access the account is still linked to your Autodesk ID.  If this is the case, we will need to ask the engineering team to purge unwanted accounts linked to your Autodesk id:   

https://forums.autodesk.com/t5/bim-360-api-forum/bim-360-api-fails-when-trying-to-connect-to-field/m...

But if you confirm, you don't have anything like that, then we will need to find what else is causing your issue. 

[Anonymous]

No. I have not used any account in the past.

[mikako_harada]

Could you try with the e-mail address registered with Autodesk account?  

[Anonymous]

Yes. Have tried that too.

[keith.white]

Looking at the original post and the attached image, I see a name in the username field rather than an email. 

When logging into the Field web UI (bim360field.autodesk.com) do you use "praveenraoATLCT" or do you use an email address?  My guess is that this is where the problem is to be found.  If you can log into the Field web UI with a set of credentials, then you can authenticate with the API using those same credentials as well, unless there are issues with inactive accounts as Mikako mentioned earlier.

I hope this helps,

[Anonymous]

As I mentioned earlier, I have tried using both email and the username to
login, with no help. Also, I was never a part of any inactive accounts or
projects.

[keith.white]

In order to use the Field APIs you must first authenticate and receive a ticket, which is what you are trying to do. This authentication must be obtained by using the credentials of a user that is active on at least one Field project. If you are not using credentials from such a user, then authentication will never be possible as this is a core requirement.

I suggest that you use such credentials to first log into the Field web interface to validate that they work as desired, then you attempt to authenticate using the API with the same credentials.

[Anonymous]

The credentials we are using is working with the field application. I'm
mapped to 4 projects and the admin for all these projects.

The same credentials is failing in API login.

[Anonymous]

Any suggestions on solving this issue? We are loosing time on this, need to know whats going wrong and where.

[Anonymous]

@Anonymous Is it possible this is being caused by a CORs issue? I'm having the same issue. I can get a ticket using the classic Field API if I use something like Python or Postman; but as soon as I switch to Javascript & Node.JS + React it stops working and presents an error message: "blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."

Is this something that I can solve at my end, or is this blocked somehow at your end?

I'm trying to run it from localhost if it makes any difference.