|
1 | 1 |
|
2 | 2 | # user-allow-list-admin-frontend |
3 | 3 |
|
4 | | -This is a placeholder README.md for a new repository |
| 4 | +This service is intended to reduce the amount of code service teams need to write, maintain and later remove for managing a list of allowed users (for example, as part of a private beta rollout). It allows you to maintain the list of allowed identifiers for services you are responsible for. Specifically you can: |
5 | 5 |
|
6 | | -### License |
| 6 | +- Add values to an allow list |
| 7 | +- Remove values from an allow list |
| 8 | +- Clear an allow list |
| 9 | +- Check if a value is in an allow list |
7 | 10 |
|
8 | | -This code is open source software licensed under the [Apache 2.0 License]("http://www.apache.org/licenses/LICENSE-2.0.html"). |
| 11 | +These actions can all be performed for multiple allow lists for a single service, by providing a "feature" argument that acts as a name for an allow list. |
| 12 | + |
| 13 | +It is used in combination with [user-allow-list](https://github.com/hmrc/user-allow-list), which is responsible for storing the list of allowed identifiers that services can check against. The [readme for user allow list](https://github.com/hmrc/user-allow-list/blob/main/README.md) provides a more complete description of what is and isn't supported, along with integration instructions. |
| 14 | + |
| 15 | + |
| 16 | +## Accessing the service |
| 17 | + |
| 18 | +Access to the service is via the `admin-frontend-proxy`, using the URL route `/administer-user-allow-list` after the admin URL the desired environment. You will be required to login using LDAP as this identifies which services you can update identifier lists for. |
| 19 | + |
| 20 | +For security and traceability purposes, any changes to an identifier list are audited including who made those changes. |
| 21 | + |
| 22 | + |
| 23 | +## Making changes to an identifier list |
| 24 | + |
| 25 | +When you log in using your LDAP credentials, you will be presented with a list of services. For example: |
| 26 | + |
| 27 | + |
| 28 | + |
| 29 | +This list is populated based upon teams you are a member of according to the User Management Portal. If you believe you are missing services, check your team membership there first. |
| 30 | + |
| 31 | +Selecting a service will provide you with a summary screen, which provides details of any features that identifiers have been added for. For example: |
| 32 | + |
| 33 | + |
| 34 | + |
| 35 | + |
| 36 | +### Adding values |
| 37 | + |
| 38 | +Using the "Add values to an allow list" option, you can add one or more identifier value for a given feature (separating multiple values with commas): |
| 39 | + |
| 40 | + |
| 41 | + |
| 42 | + |
| 43 | +### Removing values |
| 44 | + |
| 45 | +Using the "Remove values from an allow list" option, you can remove one or more identifier values for a given feature (separating multiple values with commas): |
| 46 | + |
| 47 | + |
| 48 | + |
| 49 | + |
| 50 | +### Clearing all values |
| 51 | + |
| 52 | +Using the "Clear the allow list for a feature" option, you can remove all identifier values for a given feature at once, even if you don't know the values: |
| 53 | + |
| 54 | + |
| 55 | + |
| 56 | + |
| 57 | +### Check if a value is present |
| 58 | + |
| 59 | +Using the "Check if a value exists in an allow list" option, you can check if a single identifier value is present for a given feature: |
| 60 | + |
| 61 | + |
| 62 | + |
| 63 | + |
| 64 | +## License |
| 65 | + |
| 66 | +This code is open source software licensed under the [Apache 2.0 License]("http://www.apache.org/licenses/LICENSE-2.0.html"). |
0 commit comments