Hi,
I just noticed that there was a difference in responses of the /token endpoint.
In version 8.1.2.2811 the response differs if you use a lower of upper case in the uri.
lowercase: https://{host}:{port}/v8/token
response: 
access_token <- with underscore & all lowercase
refresh_token <- with underscore & all lowercase
uppercase:https://{host}:{port}/V8/token
response: 
AccessToken <- without underscore & camelcase
RefreshToken <- without underscore & camelcase
In version 8.2.0.2008 it doesn't matter if you use 'V8' or 'v8', both responses are the same as 'v8'
Is this change intentional? Did this endpoint change, are there any other changes made that relate to uppercase / lowercase in the endpoints?
			
			
									
						
							- 
				mjr.epicfail
- Veeam Legend
- Posts: 567
- Liked: 158 times
- Joined: Apr 22, 2022 12:14 pm
- Full Name: Danny de Heer
- Contact:
change in behavior of /token endpoint
VMCE / Veeam Legend 2*
			
						- 
				JonahM
- Veeam Vanguard
- Posts: 34
- Liked: 14 times
- Joined: Sep 20, 2021 5:10 pm
- Full Name: Jonah May
- Contact:
Re: change in behavior of /token endpoint
I see the same behavior with 8.1.2.180 P20250619. I have not upgraded to 8.2 yet.
v8/token:
V8/token:
			
			
									
						
										
						v8/token:
Code: Select all
access_token  : token_here
refresh_token : token_here
token_type    : bearer
expires_in    : 3600
userName      : JonahM
.issued       : 2025-10-29T16:37:15.4708543Z
.expires      : 2025-10-29T17:37:15.4708543
Code: Select all
AccessToken  : token_here
RefreshToken : token_here
TokenType    : bearer
ExpiresIn    : 3600
UserName     : JonahM
Issued       : 2025-10-29T16:37:24.3169352Z
Expires      : 2025-10-29T17:37:24.3169352Z
Who is online
Users browsing this forum: No registered users and 6 guests