Sign-in error code management | NAGRAVISION Documentation Portal

The following table describes the use cases of error code management on clients for various cases at account and device level.

Use case	Description / use case flow	Response code	Comments
Existing user	User logs in to the account on a device and does one of the following actions on the system. Uninstalls the application Removes the application data in the browser/native system.	N/A	A new device is created for the DUT (Device Under Test) on OPF (backend hosting) linked to the account. An operator can delete or disable the device from the account.
	An operator disables the device that the user is using to access content. If content is being played, the session should stop and log out the user. Further attempts by the user to log in on the device would result in an error.	403 - Forbidden - code(20004)	If a device was disabled in error, the application needs to be removed and reinstalled.
	An operator deletes the device that the user is using to access content. If content is being played, the session should stop and log out the user. (Note that the client will only discover this on access token refresh.) Further attempts by the user to log in on the device would result in an error.	403 - Forbidden - code(20003)	Deleted device does not exist.
	An operator suspends the account that the user is using to access content. If content is being played, the session should stop and logout the user. (Note that the client will only discover this on access token refresh.) Further attempts by the user to log in on the device would result in an error.	403 - Forbidden - code(20002)	Account suspended by operator. This situation can be reversed.
	An operator cancels the account that the end-user is using to access content. If content is being played, the session should stop and logout the user. (Note that the client will only discover this on access token refresh.) Further attempts by the user to log in on the device would result in an error.	403 - Forbidden - code(20001)	Account cancelled by operator. This situation can be reversed.
	A user attempts to log in when the maximum number of devices are in use for the account.	403 - Forbidden - code(20007)	Maximum number of devices reached for account.
	The user attempts to log in or playback content using a Proxy or VPN	403 - Forbidden - code(20018)	Triggered if VPN Blocking is enabled on the platform.
	User attempts to log in or playback content from a blacklisted location.	403 - Forbidden - code(20019)	Triggered if geo-blocking is enabled on the platform.
	User attempts to log in or playback content and the token validity check fails.	403 - Forbidden - code(20020)	User attempts to log in or playback content and the token validity check fails.
	User attempts to log in or playback content from a geo filtered location.	403 - Forbidden - code(20066)	User attempts to log on or playback content that is filtered out by Geo Filtering.
	User's device tries to auto sign in.		Auto sign in failure happens and login screen is displayed on box boot up.
New user	An operator creates a new user in OpCon and the user attempts to log in with the new credentials. User should be able to login with the credentials provided by the operator.	HTTP code : 200 ( Valid credentials. ) HTTP code : 401 ( Invalid credentials. )	Success → User is logged in to the application. Failure → On screen message.
	A user logs in for the first time. A new device is created at account level.	N/A	Can be verified through OpCon. Further logout/login actions on the device should not create new devices.
	A user logs in for the first time. A new device is created at account level. Access authentication fails due to the user using a Proxy or VPN.	403 - Forbidden - code(20021)	Access was via a restricted proxy - Geo-Blocking check.
	A user logs in for the first time with a new device. A new device is created at account level. Access authentication fails due to the user's location.	403 - Forbidden - code(20022)	Access was via a restricted country - Geo-Blocking check.
	Operator disables the device the end-user is using to access content. If content is being played, the session should stop and logout the user. (Note that the client will only discover this on access token refresh.) A re-login of the user would result in an error.	403 - Forbidden - code(20004)	An on screen error is not fatal, if the user does an uninstall or removes the app the situation can be recovered.
	Operator deletes the device the end-user is using to access content. If content is being played, the session should stop and logout the user. (Note that the client will only discover this on access token refresh.) A re-login of the user would result in an error.	403 - Forbidden - code(20003)	Deleted / device does not exist
	Operator suspends the account of the end-user is using to access content. If content is being played, the session should stop and logout the user. (Note that the client will only discover this on access token refresh.) A re-login of the user would result in an error.	403 - Forbidden - code(20003)	Account suspended by operator, this situation can be recovered.
	Operator cancels the account of the end-user is using to access content. If content is being played, the session should stop and logout the user. (Note that the client will only discover this on access token refresh.) A re-login of the user would result in an error.	403 - Forbidden - code(20001)	Account cancelled by operator, this situation can be recovered.
	User is try to use the app on the max number of devices that can be used.	403 - Forbidden - code(20007)	Max number of device reached for account.
	User attempts to log in or playback content and the token validity check fails.	403 - Forbidden - code(20020)	User attempts to log in or playback content and the token validity check fails.