After a clean install of enPortal using the default configuration the following details will bring up the login screen, and after logging in, will then bring up enPortal. Please note all login page fields are case sensitive.
The table below summarizes the important URLs for accessing enPortal.
The dispatcher provides a way to bypass the login screen and pass login credentials via URL parameters. It can also be used to redirect to a different URL once logged in.
The default home is used to determine what URL to send a User to when a full path is not provided in the URL, or in cases such as when a User switches to a different Role. By default, AppBoard is configured to have itself as the home URL, but in some cases where enPortal is the main interface for end-users then enPortal can be configured as the home URL.
To override the default configuration, and have enPortal as the default home:
The following parameters can be used to automatically authenticate:
By default, it is possible to authenticate using both GET and POST requests. It is recommended to use the POST method as this avoids credentials being logged in the access log. In some environments it may be necessary to completely prevent GET logins, this can be done by editing [INSTALL_HOME]/server/webapps/enportal/WEB-INF/config/custom.properties and adding the line dispatch.loginPostOnly=true. A server restart is required after making this change.
To redirect to a specific URL after authenticating use the redirect URL parameter.
To directly access a component in Virtual Directory, use /enportal/servlet/pd/vdir/<companent reference>.