INTERNAL-Authorization

AuthorizeUser

The following routes are available for this service:
GET,POST	/authorizeuser/{Service}/{Profile}

**AuthorizeUser** Parameters:
Name	Parameter	Data Type	Required
BearerToken	body	string	Yes
Profile	path	string	Yes
Service	path	string	Yes
CustomerContext	header	string	No

**AuthorizeUserResponse** Parameters:
Name	Parameter	Data Type	Required
UserObjectId	form	Guid?	No
UserTenant	form	string	No
UserTenantId	form	string	No

**AuthorizeBaseResponse** Parameters:
Name	Parameter	Data Type	Required
IsAuthorized	form	bool	No
Settings	form	List<Setting>	No
SuggestedStatusCode	form	int	No
SuggestedResponseMessage	form	string	No
Reason	form	string	No
CustomerId	form	Guid?	No

**Setting** Parameters:
Name	Parameter	Data Type	Required
Name	form	string	No
StringValue	form	string	No
BooleanValue	form	bool	No
DataType	form	string	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv

HTTP + JSV

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /authorizeuser/{Service}/{Profile} HTTP/1.1 
Host: nkapi-sgepz3-auth.azurewebsites.net 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	bearerToken: String,
	profile: String,
	service: String,
	customerContext: String
}

HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

{
	userTenant: String,
	userTenantId: String,
	isAuthorized: False,
	settings: 
	[
		{
			name: String,
			stringValue: String,
			booleanValue: False,
			dataType: String
		}
	],
	suggestedStatusCode: 0,
	suggestedResponseMessage: String,
	reason: String
}