Security exceptions can be raised whenever you have authentication or other security mechanisms in your eSpace.

The possible security exceptions are described below:

When the Role is deleted, the exception is also deleted and all the Error handlers that caught this exception must be updated.

Usually, a security exception should be caught at the screen flow level.

Handling Security Exceptions

How to handle Security Exceptions:

Simply set the Exception property of the Error Handler to the suitable value:

  • Security: if you want to handle all the security exceptions presented above.

When catching a Security exception, the exception flow must follow to a screen with Anonymous role. Otherwise, Service Studio displays an error message and the eSpace is not valid.

  • Invalid Login: if you want to handle invalid logins situations.

  • Not Registered: if you want to handle situations where the user is not registered in the application.

When catching a Not Registered exception, the exception flow must follow to a screen with Anonymous role. Otherwise, Service Studio displays an error message and the eSpace is not valid.

  • <Role>: if you want to handle situations where the end-user does not have permission to access a given part of the eSpace.

How to set the exception

The "Security" exception is more general that any of the other exceptions, which means if an invalid login occurs and you do not have a specific Error Handler to handle it, this exception is handled by an Error Handler associated with a Security exception, if any exist.

See Also

Handle Exceptions | Exception Flow