Platform Enhancements
Enhancement to the Update Password Screens
What is changing:
On web and mobile screens where users can create a new password, we have added a checklist to aid the user in setting up their password. As the user enters their new password, the checklist will update to indicate which requirements have been met.
Items in the checklist are based on the customer’s configuration on the User Login Admin page.
Who is involved:
All customers will receive this update.
What you need to do:
No further action is necessary to implement this change.
Assign Multiple Security Groups to a User
What is changing:
ARCOS has added the ability to assign a user to multiple security groups. This can be done through the Employee Modify page, Employee Mass Modify page and the /employees API endpoint.
In the web application, the Security Group dropdown has been changed to a multi-select picker. Click and drag or ctrl+click to select multiple security groups.
Additional Notes
- For the employees API - "securityGroups” must be passed as a separate element on the employee.
- Priror to the channge security group assignments were returned and sent as: “sec_group_id” within the attributes array
-
- After the change, security group assignments will be returned and sent as “SecurityGroups”
-
- Priror to the channge security group assignments were returned and sent as: “sec_group_id” within the attributes array
- The Grant Temporary Security Access feature acts as an “and” and adds the temporary assignment to the user’s current list of security groups. No security groups will be removed.
- Assigning a user to multiple security groups acts like an “and”. If one of the assigned security groups has access, then the user will have access to the feature.
- Wherever a user’s security group is currently displayed, the user’s security groups will now be displayed coma separated.
Who is involved:
All customers will receive this update.
What you need to do:
With the 24.50 release to QA, all customers will receive this update. This change will be deployed to production for all customers with the 25.10 production deploy on Thursday, March 6. You may request this change sooner by reaching out to ARCOS Support or Professional Services.
Users should verify with their IT teams that their integrations will not be affected by the API changes prior to requesting this enabled in production. Once enabled in production, it will require manual work by the customer before we can revert the change.
IP Changes for QA and Production
What is changing:
We are excited to inform you about an upcoming enhancement to our services aimed at increasing security, stability, and reliability. As part of this initiative, we will be leveraging AWS services, which require an update to ARCOS IP whitelists to ensure seamless connectivity.
Action needed by you if you whitelist access to ARCOS web back office:
We request that you update your firewall whitelists to include the new AWS IPs ARCOS will be utilizing and have been included below. The new IP whitelist is also published in ARCOS Online Documentation found in the ARCOS OSCAR portal. To ensure uninterrupted access to our services when we migrate to the new services, we ask that you have all new IP whitelists added before the ARCOS 24.48 release for QA: November 8, 2024, and before the ARCOS 24.50 release for Production: December 12, 2024. The existing whitelist should not be removed for either QA or Production until the ARCOS 25.02 release on January 9, 2025.
QA:
- 15.197.215.121
- 76.223.75.28
PROD:
- 13.248.204.4
- 76.223.38.174
If you have any questions or need assistance, please do not hesitate to contact our Support Team.
Comments
0 comments
Please sign in to leave a comment.