RESTful knowledge exchange
Post Reply
Cragdoo
Veeam Vanguard
Posts: 584
Liked: 232 times
Joined: Sep 27, 2011 12:17 pm
Full Name: Craig Dalrymple
Location: Scotland
Contact:

v11 - oauth url

Post by Cragdoo »

Hello

I'm working with a monitoring solution ( Squared Up Dashboard server) and looking to utilise the new v11 REST APIs for VBR. When trying to add the VBR server, I need to provide the following information

authorization URL
token URL
client ID
client secret

Image


I'm guessing the authorization url is

Code: Select all

/api/oauth2
token url

Code: Select all

/api/oauth2/token
but not sure about client ID / client secret .....username password?

Cragdoo
Veeam Vanguard
Posts: 584
Liked: 232 times
Joined: Sep 27, 2011 12:17 pm
Full Name: Craig Dalrymple
Location: Scotland
Contact:

Re: v11 - oauth url

Post by Cragdoo »

actually bigger problem is the requirement for the

"x-api-version: 1.0-rev1"

header to be sent on the authorization request.

veremin
Product Manager
Posts: 18450
Liked: 1828 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: v11 - oauth url

Post by veremin »

Does this section of our User Guide answer your question about how authentication requests should be constructed? Than

oleg.feoktistov
Veeam Software
Posts: 915
Liked: 325 times
Joined: Sep 25, 2019 10:32 am
Full Name: Oleg Feoktistov
Contact:

Re: v11 - oauth url

Post by oleg.feoktistov »

Hi Craig,

I’ve never worked with Squared Up Dashboard server, so not sure about the terminology it uses.
But from what it looks like to me, your understanding about client id/client secret is correct.

And what is the issue with the versioning header?

Best regards,
Oleg

Cragdoo
Veeam Vanguard
Posts: 584
Liked: 232 times
Joined: Sep 27, 2011 12:17 pm
Full Name: Craig Dalrymple
Location: Scotland
Contact:

Re: v11 - oauth url

Post by Cragdoo »

Thanks for the replies.

It's probably more an issue at my end, with the terminology.

Regarding the header issue, again issues at my end (unable to send x-api-version) but got me thinking
a) never had to set api-versiobn before in other product calls (Enterprise Manager/VO365)
and
b) if according to the reference guide "In the x-api-version header, the current revision of the Veeam Backup & Replication REST API must be specified."
where can I find a list of the versions, to ensure I'm using the current revision?

oleg.feoktistov
Veeam Software
Posts: 915
Liked: 325 times
Joined: Sep 25, 2019 10:32 am
Full Name: Oleg Feoktistov
Contact:

Re: v11 - oauth url

Post by oleg.feoktistov »

a) There are few different versioning approaches to REST. On authentication step for EM, for instance, you need to specify version in the URL itself. In REST for VBR we use a combination of URL versioning and a versioning header.

b) The most current revision is listed here.

Thanks!

Cragdoo
Veeam Vanguard
Posts: 584
Liked: 232 times
Joined: Sep 27, 2011 12:17 pm
Full Name: Craig Dalrymple
Location: Scotland
Contact:

Re: v11 - oauth url

Post by Cragdoo »

Thanks Oleg

Missed that revision list.

Are there plans to standardise the REST authentication/methods/urls port going forwards?

veremin
Product Manager
Posts: 18450
Liked: 1828 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: v11 - oauth url

Post by veremin »

We do not have any short-term plans, but what approach out of two you prefer and why? Are there any specific requirements you have or it's more like universal approach request? Thanks!

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest