ARAS 31 soap-env:server authentication failed for admin authentication failed for admin

Hi Salini,

The password grant authentication option was deprecated in R14, so you’ll need to update your application to use the OAuth 2.0 login flow. 

Here’s a blog post demonstrating how to get an access token via Postman: https://aras.com/en/blog/authenticating-in-oauth-2-0-with-aras-restful-api

And here’s a sample console application that shows how to authenticate with an access token via .NET Core: https://github.com/ArasLabs/rest-auth-example 

Hai Eli Donahue,

Thanks for the response, I have tried as mentioned, I have generated access token successfully,

but I could not find the odata/Part in my server. After that I could not proceed.

any thought on this?

Thanks in advance

Salini 

Hi Salini,

What happened when you sent the request? Did you get an error message or did the server return “no items of type Part found”?

Hai , 

I can able to generate the access token successfully , But the parts are always empty array .I have tried with the BRUNO , even though the parts returns as empty array. 

And also we are using a .NET framework console application . Could this be a problem .

I have tried to create a .CORE application to populate the parts but the await method exit the application automatically . 

Can you help me with this please ?

Thanks in advance .

Regards

Salini V

Hai Eli Donahue,

I have fixed the issue 

I have added the ODATA services into the nnovatorServerConfig.xml

<Service Enabled="true">

<Name>OData</Name>

<Route>/server/odata</Route>

<Handler>Aras.Server.OData.ODataHandler, Aras.Server.OData</Handler>

</Service>

and added the line <Scopes>Innovator OData</Scopes> into the oauth.config file. 

And restarted the server.

Now I can able to access the parts , Thank you for your guidance through out the conversation . It was very helpful . 

Regards

Salini 

Ah, it sounds like the scope was the issue. When requesting a token from the OAuth server, it’s important that the client id and scope(s) match the OAuth config file. Otherwise the request will fail. 

I’ve never had to modify the InnovatorServerConfig.xml file the way you described though, so that part may not be necessary.