Postman, Swagger showing You are not authenticated!

Hey @Razvan_Dumitru

Just a quick question please, So you mean that this how it is going to be ?

Or the steps which you mention is just if we face auth issues on swagger ?

Thanks
#nK

Hey @Razvan_Dumitru,

The above mentioned steps I have to do in the Orchestrator tab or in the Swagger tab ?

And one more thing, this step I have to follow every time when I will check any API call in swagger ?

Thanks,
Sanjit

1 Like

Hey @Sanjit_Pal

Those steps should be done on chrome browser developer console, from where you opened the swagger.

Thanks
#nK

Hey @Razvan_Dumitru,

I have done the same as you have explained, still having the same issue.
image

Thanks,
Sanjit

1 Like

Hey @Sanjit_Pal

Are you using any ad-blocker or something ?

Just thinking if something is blocking !

Thanks
#nK

Hi @Sanjit_Pal1 Instead of PostMan please try the below

Hey @KIRTI_IYER,

It’s working fine with the uipath orchestrator HTTP request activity.

I am only facing the issue with Postman and Swagger.

Thanks,
Sanjit

It doesn’t seem that you have a contextual access token. Can you please double-check if the Authorize button from Swagger page has a lock in locked state?

It seems that your curl command misses a Bearer authorization header:

Hey @Razvan_Dumitru

PFA the screenshot below

The authorize button is not in the lock state. Once I have clicked on the Authorize button the popup opened.

In this pop up there are two field client_id: and client_secret:, from where to get these two value to authorize.

Thanks,
Sanjit

Please see here on how to generate those two values:

And this guide goes in depth over the Swagger authentication flow:

@Sanjit_Pal Basically you’ll just need to press Authorize. Client_id/client_secret are already known and configured in behind.

Hey @Razvan_Dumitru

Just curious to know, on what basis does that Authorize button appear as I can’t see it !

Thanks
#nK

Hey @Razvan_Dumitru ,

If I am trying to authorize it by clicking on Authorize button, it’s redirecting me to the below page.

Thanks,
Sanjit Pal

@Sanjit_Pal can you please help us with a .har/network export in order to better understand what’s happening in your case?

Did you modified client_id/client_secret?

@Nithinkrishna Swagger Authorize button is tightly coupled with cookie to access token based authentication migration.

This feature is currently in rollout phase and it will be available to all users next week.

1 Like

Hey @Razvan_Dumitru can you please help us with a .har/network export in order to better understand what’s happening in your case? - How I can do this?

Did you modified client_id/client_secret?- No I have not did this

Thanks,
Sanjit

Hi @Sanjit_Pal

Step by step would be to:

  1. Be logged in Orchestrator in one tab
  2. Open a new tab
  3. Open the browser console in that new tab (CTRL+SHIFT+I on Chrome) and navigate to the Network tab
  4. Paste the swagger URL in the new tab and let it open
  5. You will now find an arrow icon on the Network console toolbar that will allow you to save the network log.
  6. Please share it with @Razvan_Dumitru via a private message (do not post it in this public thread)

Thank you :slight_smile: :+1:

@Sanjit_Pal Were you able to obtain a token for your Swagger?

You might encounter that error if orchestrator_ path is not specified in your Swagger url.

So, if you’re using:
https://cloud.uipath.com/yourOrganization/yourTenant/swagger/index.html,
can you please try to specify the orchestrator_ path?
https://cloud.uipath.com/yourOrganization/yourTenant/orchestrator_/swagger/index.html

@Razvan_Dumitru Getting the same issue with url.

Have a look on the attached screenshot, the authorize button is still unlocked.
https://cloud.uipath.com/yourOrganization/yourTenant/orchestrator_/swagger/index.html


Thanks,
Sanjit