The Coins ERP+ user ID is stored in a cookie after a successful login. It is retrieved for a new login and the User ID fill in is defaulted to its value by the login screen. This only occurs if the browser setting allows the use of permanent cookies.
To allow users to log in using their email address, a unique email address must be entered for the user in Users.
For more information about logging in using Azure Active Directory, see Setting Up AAD Single Sign-On.
Pre-login messages
You can display a pre-login message to alert users to upgrades or downtime or other important information. They have to click the Go To Login button to proceed to the login page. This sets a cookie, which means each user will only see the message once (unless they clear cookies, or use a different browser or device).
Example Pre-Login Message
Create an HTML file containing the message.
The content of this message needs to render in the context of the right hand side of the message page. Ideally it should be self contained HTML. Any references to external content MUST be in the content security policy for the site.
Place this file in the shared folder $BASE/var/home/messages/. You can create many different message files; only one is shown. Specify which message to show using the SY parameter PRELOGIN.
This is separate from the Coins pre-login message, which is configured by Coins.
Login screen
The navigation buttons to Guides and Documentation and Support are fixed but can be overridden if required using the SY parameters DOCBASE or DOCBASEL and SUPBASE or SUPBASEL. The back button in the navigation will only appear if the coins.json file has been created. It will link to /coins/menu/index.html (default). It can be overridden if required where a test system is on a different server by setting the CCCHOME parameter to https:<hostname>/coins/ where <hostname> is where the menu is installed (presumably the live server).
Parameters
sy/docbase
Base path to COINS documentation portal
The path to the COINS Help Portal. This is also used for the Documentation link on the Coins ERP+ login screen unless you override it using DOCBASEL.
The COINS Help Portal is hosted on the COINS website and includes information about features of COINS, processes instructions, and set up and configuration details. It can be accessed using the Documentation item on the Coins ERP+ user menu, or by following links in the side-frame help.
If DOCBASE is blank, COINS documentation is taken from the UK and Ireland version of the Help Portal.
sy/supbase
Base path to COINS support
The URL for the support link in the Coins ERP+ side-frame help. This is also used for the Support link on the Coins ERP+ login screen unless you override it using SUPBASEL.
This is optional and overrides the default link, which is to the support area of the COINS website.
To suppress the button, set SUPBASE to !.
Related Parameter
Base path to COINS support on login
An optional URL for the Support link on the login page. This overrides SUPBASE for the login screen and lets you provide a different support option for users who have not yet logged in.
Construction Cloud Home Page
The URL of the COINS Construction Cloud home menu page.
If this is blank, /coins/ will be used on the current server. If a live and test server are used this needs to be set to <livehost>/coins/ to redirect the test host to the live server for the menu.
Prelogin message file
The name of a file in $BASE/ var/ home/ messages to be presented as a client prelogin screen.
You can configure a message to alert users to upgrades or downtime or other important information. Users must click the Go To Login button to proceed to the login page. This sets a cookie (COINS.<env>.prelogin) so they do not see the message more than once.
The content of this message needs to render in the context of the right hand side of the message page. Ideally it should be self-contained HTML. References to external content should be avoided, but if present MUST be in the content security policy for the site.
If SY/PRELOGIN is blank, COINS does not display the client prelogin screen.
Check password strength
Whether a user's password should meet certain strength criteria.
If you set this to Y then passwords will need to be at least 6 characters long, and contain upper and lower case alpha, numeric, and special characters.
COINS recommends turning this parameter on to enforce strong passwords. Clients should configure this to align with their corporate standards.
Show password reset option on login page
Whether to display the Forgotten Password option on the COINS login screen (Y or N).
This allows a user who has forgotten their password (or whose account is locked) to request a link to be sent to their email address; the link allows them to reset their own password.
Allow re-login
If you are using operating system logins (specified in Menu System Configuration), are users allowed to log in immediately after they log out?
Y = Users are taken to the COINS log in screen when they log out.
N = Pressing F4 logs the user out and returns them to the operating system. The parameter LOCKTERM determines what happens if the user presses L.
If you are not using operating system logins, users are always given the option to re-login.
Number of invalid login attempts allowed
The number of invalid login attempts which are allowed before a user's account is locked out.
If the allowed number of invalid login attempts is exceeded, COINS automatically ticks the Account Locked box on the user's record. The user will not be able to log in to COINS using any interface until this box is unticked.
This also applies when a user changes their password.
COINS recommends setting accounts to lockout after multiple login failures (between 3 and 10). Clients should configure this to align with their corporate standards.