This repository has been archived by the owner on Mar 30, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
2. User Accounts
Tim Davis edited this page Dec 8, 2017
·
3 revisions
After installing AmSYS to your server, configuring the properties file, and running the setup commands, the next step is signing in to the system!
The first account you create should be your own System Admin account. This allows you to modify configurations and control access for other users.
- Navigate to http://your.com/ (wherever your virtual host for AmSYS is configured for) and sign in using EveSSO. The first time any user signs in, an account is automatically created for them in the Users table with a default ROLE.
- To change your own ROLE, log in to PHPMyAdmin and load the Users table. Change your user's
override_role
to ROLE_SYSTEM_ADMIN and save. - Logout of AmSYS and log back in, you now have system admin permissions!
Now that you are a System Admin and are able to manage the application settings, you should configure who can access your system and how.
- Log in with a System Admin account and navigate to System > Access Control > Authorization on the left
- Guest Access
- By default the 'Default Access (Everyone Not Configured)' is set to ROLE_MEMBER. This means anyone can log in to the system but they still can't sell anything. If you'd like to let anyone sell to you, select 'ROLE_ENTITLEMENT_BUYBACK' from the Applied Entitlements dropdown.
- Authorized Access
- Set Default Access to 'ROLE_DENIED'
- Type your alliance name in the box and hit 'search'. Choose the correct alliance from the list (double click) and they should be added to the manual authorization list. You can set their role to 'ROLE_MEMBER'.
- Don't forget to add 'ROLE_ENTITLEMENT_BUYBACK' so that they can use the buyback system.
- You can also add a character API key/code to pull a list of personal, corporate, and alliance contacts and base roles off of contact levels. When doing this, note that your own Corp/Alliance are likely not on the contact list and will not be granted roles through this. If you configure an API, you can have it periodically update itself by following the guide to set up a cron job.
The next step is to set up Cron Jobs for scheduled application tasks