Only this pageAll pages
Powered by GitBook
Couldn't generate the PDF for 197 pages, generation stopped at 100.
Extend with 50 more pages.
1 of 100

3.1.6

Getting Started

Loading...

Release Notes

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Personalization

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

API Client

Batch Tasks

Loading...

Loading...

Identity Hub

Managing Users and Groups

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Delegation

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Identity Provider

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Logs

Loading...

Loading...

Loading...

Lifecycle Management

Loading...

Loading...

Getting Started

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

3.0.2-Beta

Version: cloud_3.0.2-beta product release

Date: 01 December 2023

**To ensure the highest quality standards, some features in this version are marked for further refinement and will not be included in the current release. Please refer to the next approved release for updates and improvements.**

New Features

  1. User management service restructured.

  2. PAM - Sub domain added in Authentication Parameter

  3. UI/UX Improvements:

    • Show username in user selection dropdown menus

    • Show Cymmetri Verify app link on MFA TOTP Registration and App MFA TOTP, Push, Fido

    • Show message when cookies are disabled on browser

    • Cymmetri Verify App update (v5.10)

      • App drawer, header and lock screen UI improvements

      • Search box moved to header

      • Show search history

      • Haptic feedback on TOTP code press

  4. Cymmetri Verify App Hotfix (v5.10.1)

  5. Introduced spring expression language in SAML.

  6. In Multifactor otp config we can't disable both email otp and sms otp. At least one should be active.

  7. Group Provisioning

  8. Cymmetri Mobile App update (v1.5)

    • Added QR code self registration for TOTP, Push and FIDO

    • Added TOTP self verification eliminating need for finding and copying TOTP from cymmetri Verify app for the login

    • Added App lock with biometric in the app

Fixes

  1. Forgot password-User is not receiving email notification

  2. Workflow description spelling correction

  3. Workflow on unassignment-On role unassignment, if any workflow already trigger then message should be shown

  4. Manage view- for converter used parameter not showing

  5. Application-date converter, recon pull getting stuck

  6. Workspace | click search box creates Ul glitch

  7. Login with Read only user- Configuration> Syslog configuration- Configuration should be gray out and should not be editable

  8. Configuration>User decommission config- Add a short description specifying functionality (Title)

  9. MFA- Rename SMS Authenticator to OTP Verification

  10. Configuration>Master>Zone>Gateway IP- Sorting is not working

  11. Configuration>Master>Global>Value- Sorting is not working

  12. Configuration>Master>Zone>Name- Sorting is not working

  13. User Onboarding| Contact info details not accepting other country mobile number

  14. Delegation- Successful Validation message should be shown after user is assigned

  15. Time-based role assigned application- Time based Application is not getting deleted after time period is completed when role is assigned

  16. Configuration>Master>Zone- Showing old zone data when creating new zone

  17. My workspace>Access Review>IG>Managed - When all the checkbox of Info field are disabled, then title checkbox should also be disabled

  18. Provision- When user is trying to create new role, role is not getting added neither validation message is shown

  19. Cymmetri Verify - IOS - Push/FIDO Verification screen not shown when app opened through its notification

  20. Cymmetri Verify - App protection not working

  21. Self service app- User when trying to login on self service app having Fido authentication On, user is redirected to Play store but see in play store app is not clickable

  22. Cymmetri Verify - Same day exported file - with file count attached to the name is reported as invalid file

  23. Application provisioning MFA- When max TOTP/OTP/Secret Question invalid answers limit exceeds, it should show validation message and should be redirected to login page.

  24. Application Role workflow- User is applying workflow for specific role but non workflow as signed role is also not getting assigned

  25. Update user import sample file

  26. usersrvc/api/user/dropdownList- in above path, for create workflow in bulk

    when we create in bulk it is showing out of memory

  27. Global Notification disable-by default it is off

  28. Notification template- Global Notification for OTP is off still logs is showing mail sent(True)

  29. Campaign with group-Campaign getting aborted

  30. Multi-role assignment with form, then form adding repeatedly for each role, expected only one form should be there

  31. Deprovision rule- User is not getting suspended when end date is applied at the time of user creation

  32. Users Import- User name, Login should get trim if space is included while importing user

  33. Identity Hub> User session- User session is not getting terminated even after revoking users session button is clicked

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

What is Cymmetri?

What is Cymmetri?

Cymmetri is a Converged Identity & Access Management Platform and a well-trusted platform acting as an advisor and an end-to-end partner for Security-aware teams looking to deploy Identity and Access Management Solutions across their organization.

We offer an industry-standard product backed by a strong team that always aims to innovate our solutions to cater to a wide variety of enterprise needs.

3.0.3-Beta

Version: cloud_3.0.3-beta product release

Date: 15 December 2023

**To ensure the highest quality standards, some features in this version are marked for further refinement and will not be included in the current release. Please refer to the next approved release for updates and improvements.**

New Features

  1. WebAuthn passwordless authentication (It only works for chrome, safari, edge on desktop and chrome and edge on mobile) - EXPERIMENTAL

  2. Onbehalf Configuration

    • Default onbehalf configuration

    • Rule engine support to create custom configuration.

    • Display the OnBehalf menu in self-service according to the logged-in user's matching custom/default configuration.

    • Below menu operations supported

      • User Application View,

        • Assign Application

        • Assign Role

        • Unassign Application

        • Unassign Role

      • User Groups View

        • Assign Group

        • Unassign Group

    • Group Provisioning Enhancement

    • Policy map datatype converter Enhancement

      • Converter support added in custom attribute

      • Configuration support added for custom attribute converters

      • Encryption added for Custom attribute password converter value of user

      • Bug fixes

      • Bug fixes

      • Added self verification support for forgot password, App MFA, server MFA, and passwordless

    • Global module search feature (Ctrl+K)

    • Groups list pagination in user details

    • Connector

      • Oracle HCM

    • PAM

      • AD seperated from the Cymmetri

    • Group - View Attribute - Showing list of CN of members of remote group

Fixes

  1. Workflow for time-based role application- Audit log should show action not supported me ssage if lifetime application is changed to time base from approver end.

  2. Recon Link for both exist- When updating group after linking showing custom attribute error

  3. Multi node-Application assign with role, all user getting assigned but still import showing in progress

  4. AD group count mismatch-In AD total 1278 group but in pull it is showing 1260

  5. Application Group- Pagination should be applied for group provision page

  6. AD application push- Group should not be updated when update checkbox in policy map is unchecked

  7. AD Recon Push- When all policy attribute are false, group creation should show error.

  8. AD Application Pull- When all policy attribute are set to false, group creation should show error

  9. AD-Policymap_memberOf need to be default false for old tenants

  10. Browser specific-On Mozilla browser OTP verification is not proper

  11. Login with Domain Admin- Manager assignments should not be greyed out

  12. Import completed file show end time

  13. Policymap-group(pull/push)-if attributes are inactive then this should not be reflected under dropdown

  14. PAM-Sign on Policy- Policy should not get activated unless MFA factor is selected.

  15. Audit-Configuration-OTP-For check uncheck Send OTP on,audit should be present

  16. AD application- Should show error message when description is user principal

  17. Self service-Read auto MFA considering camel cases

  18. Cymmetri Verify app- Cymmetri mobile app is not able to fetch TOTP from verify app if the re are more than 20 TOTP users

  19. Users Managed View- Managed view should get blank for those application not supporting this operation

  20. Configuration>Master>Browser Tab text is not correct

  21. Workflow- Close button in Users details pop up box should be enlarged (currently not visible properly)

  22. Branding-Should show proper validation message on UI

  23. Version-provisionsrvc showing two times

  24. PAM> SignOn Policy- Discard button is not working

  25. Identity Hub> Users: Others field details are not visible on user display page on editing profile

  26. Cymmetri app(selfservice)-Auto read MFA-when Cymmetri verify app having App protection is enabled then also it is reading,bypassing app protection

  27. Cymmetri Verify - Google Authenticator Import TOTP timer not running

  28. Cymmetri Verify - MFA Push Registration fails

  29. Cymmetri Verify - App crashing on Samsung fold phone

  30. SAML-Expression-restrict to show id

  31. SAML-Expression-if user don't have data and fetching data then no message showing on UI

  32. SAML Key:- Not able to understand why validation message is showing invalid arguments

  33. Delegation- Session getting expired even after refreshing token continuously

  34. External idp login showing error

  35. SAML-User is not able to download metadata, showing 500 internal server error

  36. API SSO validateToken API only validate the auth_key parameter

  37. Password converter only accepted encrypted value. it should also accept user's editable va lue

  38. Identity Hub>Group: Grey out Group name field for remote groups as user cannot edit name

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

  3. Application getting assigned from UI. If it is failed.

  4. Group-Custom Attributes not getting updated in group while assigning user to the group manually

Cymmetri Verify v5.10.3 - () -

Cymmetri Mobile v1.5.1 () - (Rejected)

link
link

3.0.6-Beta

Version: cloud_3.0.1-beta product release

Date: 30 January 2024

New Features

  1. Provision Rule Revamp:

    1. Restructure Provision rule condition configuration

      • Provide support single condition and group condition in condition config.

      • Provide Operator support like Equal and Not Equal.

      • Provide AND , OR Operator support for multiple condition in provision rule condition config

    2. Group provision Support

      • Add group in provision rule. (only local group)

    3. Old provision rule migration

      • If old rule without condition mark as inactive.

      • if old rule without application also mark as inactive.

  2. UI/UX Changes:

    • Application profile and group mapping in SAML SSO

    • SAML Service Provider - Restructuring and provide defaults

  3. Deprovision Rule support for user delete (if no application assign)

  4. SSO -SAML

    • SSO-group policy Mapping -- SSO SAML.

    • SSO-added nameFormat in profileMapping and groupMapping -- SSO SAML.

    • SSO-added digest algorithm method.

    • SSO-added list support for profile mapping.

  5. Mfa Attempt Enhancement(Old behaviour when admin locks the user then user should not able to unlock from selfservice now he/she can able to unlock yourself)

    • user can unlock if admin locked the user

    • invalid mfa will permanently lock the user, user can unlock account after mfa cooldown period is completed.

    • admin can unlock the user which will unlock the mfa as will

  6. UserType Master Support in User Creation and Updation.

Fixes

  1. Provision Rule- Rule is not getting applied if previous provision rule is deleted.

  2. Group- Search functionality is not working

  3. Not getting form values in the target application when Form updated, role assigned and role unassign

  4. Self service app- Increase spacing

  5. Notification bell icon- When notification is empty, mark read and delete option should not be clickable

  6. Cymmetri self service app- When clicked on groups or application from on behalf tab, it is redirecting to dashboard page

  7. User Onboarding| Contact info details not accepting other country mobile number

  8. Cymmetri Verify app- For long tenant name timer clock is not visible

  9. Group-Attribute detail-provide search

  10. Android Heads Up Notification now will display notification upfront which earlier required from user to turn on from the Notifications Settings (Float Notification)

  11. Notification template-correct spell for delegation

  12. Deleted user login-on forgot password this user should be validated and restrict,currently showing error-Please try again

  13. SAML-On clicking validate regular expression should show data message which is available in backend

  14. Ctrl+K: Search filter is showing records for all the letters mentioned

  15. If the admin lock the user, then the user should be able self unlock by forgot password flow

  16. Audit- Audit log should shows role specific logs for role assignments/ unassignments

  17. Self Service: Access review- Validation message is not complete it is getting cut

  18. Registration- Showing processing please wait validation message after registering user and without any setup if user is clicking logout

  19. Self service app-On behalf: When clicked on application/groups from dropdown mobile keyboard is getting displayed and due to that applications/ groups visibility is less

  20. Not getting form values in the target application when form updated, role assigned and role unassign

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

  3. Workflow initiated for form but form is getting updated without workflow approval.

3.0.9-Beta

Version: cloud_3.0.1-beta product release

Date: 03 November 2023

**To ensure the highest quality standards, some features in this version are marked for further refinement and will not be included in the current release. Please refer to the next approved release for updates and improvements.**

New Features

  1. Provide show to user flag support in Application Setting .

    • Application Setting

      • show to user

        • If flag is off,then hide application from my access ➝ assigned application.

        • Delegation : If flag is off,then hide application from Delegation ➝ my access ➝ assigned application.

      • user can request

        • If flag is off,then hide application from my access ➝ request for assign application.

        • If flag is off, then hide application from On-behalf ➝ users ➝ request for assign application.

        • Delegation : If flag is off, then hide application from Delegation ➝ On-behalf ➝ users ➝ request for assign application.

  2. Framework Upgrade: Java based services are updated for spring framework, spring boot, also updated utility libraries. Please note it may have impact on several functionalities.

  3. MFA attempt Admin User lock

    • MFA attempt config added in global auth policy

    • Self unlock flag to unlock the user during admin lock the user

  4. Token Rolling period : Token start period should start before current server time.

  5. Passwordless reset password : When password is required to be changed then user is forced to change password during login using passwordless.

  6. Bearer Token subject is encrypted now in header.

  7. cookies samesite attribute is being set to strict to all the cookies.

  8. Active Directory new bundle (Using unboundid.ldap.sdk library) - Phase 1

    • Server Connector bundle name: simpleADServer Connector bundle version: 1.0Server Connector name: com.cymmetri.connector.simple.ad.SimpleADConnector

    • Added one field inside user configuration of active directory "Disable User With Date Time".

Fixes

  1. Policy Attribute- Add pagination

  2. Teams Configuration- Showing route issue when saving new teams configuration

  3. Passwordless- Passwordless page is showing blank when clicked on clicked on Passwordless button on Login page

  4. Notification template- Increase spacing between Kathreftis Team and Disclaimer and remove space above

  5. Login failed> User locked Template- Change notification template

  6. My access> Applications- If an application is already present in a certain tag, when attempting to move it to another tag within the "All Applications" section, it should not be visible in the tag it is already associated with.

  7. Login-Tab button should be applicable for enter password field when passwordless in enabled

  8. AD Application- When assigning remote group to AD user, showing error

  9. Passwordless- Passwordless page is showing blank when clicked on clicked on Passwordless button on Login page

  10. Self-service app: On-behalf tab is loading late

  11. Master> Zone- When editing zone then status is always changing to inactive

  12. Authentication Rule- When user is trying to reset password having LDAP authentication active, then password is changing into target system first and reflecting older password in target system

  13. PAM- Dormancy disabled config- By default config should be disabled

  14. Audit-"action":"DORMANCY_DISABLE_COMPLETED" ,Data showing null,need to show data

  15. PAM dormancy disabled showing failed

  16. Deprovision- All three fields should be in one line

  17. Policy Attribute- Add search filter in policy attribute

  18. Delegation- Add cancel button after editing consent

  19. My Access> Applications- When moving application from one tag to another, then validation message should be proper for end user to understand

  20. Campaigns> Access Review > Campaign Manager- Sorting is not working

  21. My Workspace> Inbox- Need to refresh page every time to see changes in started request

  22. Global Auth Policy- Update message to "Auto Unlock MFA period should be less than Account Auto Unlock period."

  23. Insights> Reports -Showing error message when disabling scheduler toggle

  24. Application MFA update -on click Next button -getting in loop

  25. PAM vault user-Confirm button should not be enable till any value entered

  26. Validation message change-Change 1 days to 1 Day

  27. Teams Config- Configuration should not be saved without adding condition

  28. Teams - User is not able to lock/unlock account even after configuration in teams is enabled

  29. Need to show proper error message when Maximum MFA attempts reached

  30. Reset Password OTP -there is only OTP option is available then also showing error message for question

  31. MFA- User not able to login via Consent based MFA showing error

  32. Login- Showing error when trying to log in using secret question as MFA

  33. Teams Configuration- Showing route issue when saving new teams configuration

  34. MFA count gets reset, when admin mark lock to unlock

  35. MFA- User is able to unlock account event after unlock user account time is not completed

  36. Login with password less-password expiry should be consider and need to follow steps to reset

  37. When admin lock user the take conformation, unlock yourself or lock lifetime

  38. End date over user login-on forgot password this user should be validated and restrict,currently redirecting on MFA

  39. Inactive user login-on forgot password this user should be validated and restrict,currently redirecting on MFA

  40. Need to update audit when user attempt max MFA

  41. MFA- User not able to login when user is trying to login using normal password flow

  42. My workspace> Active Campaign- Latest selection should remain as it is.

  43. Pagination persistence for users (when a user clicks on lets say 3rd page and go into the user details and when come back the pagination gets reset )

  44. Application provisioning workflow- Assign application to user and then cancel it, still showing user assigned

  45. My Access>Application> Tag- Search filter should be applied for tag applications as well

  46. Add New Application Search , when no data is there the UI breaks and a No Data Found card should also be shown on screen

  47. Login Page- User is not redirecting to mentioned login help page( Mentioned in Branding)

  48. Cymmetri Mobile App- Changes required in secret question layout on login page

  49. User Creation Workflow- When clicked on the cancel button on the workflow preference popup box, it should remain on the user creation page. For now it is cancelling the whole process

  50. Branding- Show validation message if user miss to fill any fields and clicked on save button

  51. Lifecycle mgmt>Workflow Configuration- Save button should be enabled when removing approver.

  52. Suspend user-For device deleted message should be shown as Device Deleted

  53. User Onboarding- When provision rule is trigged while onboarding user and any application is assigned to user then assigned tag should be shown in that application as showing in Groups

  54. Configuration> Master- Accepting emoji values in Global Master

  55. MFA- Secret question- Answer field should get blank after question is selected.

  56. Delegation- After delegation time is completed, delegation configuration should be updated

  57. Authentication Rule- When user is trying to reset password having LDAP authentication active, then password is changing into target system first and reflecting older password in target system

  58. Global Auth- User should be able to set Account unlock and MFA unlock to minimum 1min

  59. User-Account lock-Account is self lock then also on UI showing message user cannot unlock

  60. User Setting- Showing user not found error message

  61. Lifecycle Management || Applications redirects user to Identity Hub

  62. Campaign- UI of Calendar field is not proper

  63. Policy attribute- When removing policy attribute, that field is not getting removed also it is visible in policy map application field dropdown

  64. Audit Log- When duplicating a tab and subsequently refreshing it, then audit log is displaying a random requestor ID

  65. Global Auth Policy- "Allow Users to have" is displayed twice

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

  3. Workflow initiated for form but form is getting updated without workflow approval.

  4. In application setting if show to user flag off then also application show in recent application.

3.0.5-Beta

Version: cloud_3.0.5-beta product release

Date: 12 January 2024

3.0.1-Beta

Version: cloud_3.0.1-beta product release

Date: 03 November 2023

**To ensure the highest quality standards, some features in this version are marked for further refinement and will not be included in the current release. Please refer to the next approved release for updates and improvements.**

New Features

  1. Policy Map Datatype Converter

    • Added standard converter to convert ldap profile picture.

    • Added standard converter to encrypt & decrypt data.

    Sample Fields For Active Directory

  1. Decision Engine Restart Scheduler

    • Added scheduler which will run on every hour and process stuck decisions.

  2. Audit JMS Queue added in following services

    • cymmetri-microservices-authPolicy

    • cymmetri-microservices-mfa

    • cymmetri-microservices-notification

    • cymmetri-microservices-provisionEngine

    • cymmetri-microservices-registration

    • cymmetri-microservices-ruleEngine

    • cymmetri-microservices-selfservice

    • cymmetri-microservices-usermanagment

    • cymmetri-microservices-workflow

    • IG

    • cymmetri-microservices-sodengine

    • cymmetri-microservices-pam

    • cymmetri-microservices-analytics

  3. UI/UX Changes

    • Show Cymmetri Verify app link on push/fido registration screens.-Rejected for the selfservice app

  4. Cymmetri Verify App update (v5.9.1)

  5. Cymmetri Verify App update (v5.9.2)

  6. Cymmetri Verify App update (v5.9.3)

    • Display a message to indicate the action being performed

  7. Restructured bulk user import for performance

  8. Notification Global Config

    • Notification categories in two types i] Mandatory ii] Optional.

    • Notification Global Config applicable for only optional type of notification.

Fixes

  1. Cymmetri Verify- When exporting TOTP users password is accepting all digits/values as alphabets/number when it should have accepted alphanumeric values

  2. Cymmetri Verify | IOS | Face ID being asked infinitely

  3. Cymmetri Verify app- Showing duplicate records when imported from other device

  4. Cymmetri Verify app- Search functionality is not working when users imported from different device

  5. Cymmetri Verify- Show password when clicked and file is exported, then again export file same password is visible with no masking(password is visible)

  6. Cymmetri Verify | IOS | Unable to import backup file

  7. Cymmetri Verify | IOS | Face ID not supported error

  8. Cymmetri Verify | Account details not updated on adding/removing push/fido

  9. Cymmetri Verify | IOS | Not internet error

  10. Application getting repeated within different pages of application list

  11. My workspace>Access Review>IG>Managed - When all the checkbox of Info field are disabled, then title checkbox should also be disabled

  12. User - Application - Group name should be displayed

  13. Audit-Audit with device filter not working

  14. Vaulting Configuration- Test connection audit not present

  15. Notification Template- User is not receiving mail for reset password

  16. Login-Showing incorrect validation message and asking user to reset password again

  17. Onboarding flow | Additional details not accepting other country mobile number

  18. Recon history- provide search

  19. Tenant Registration- Domain is not visible

  20. Register tenant- Country dropdown is showing no option instead of countries list

  21. Application - Tag - Already created tags present in application are not getting displayed in grid page.

  22. Partner Portal- Showing invalid argument but not able to understand exact which field is invalid

    • Admin Portal- Top search not working

    • Admin Portal- Get Started link not working

    • Admin Portal- Company name and company code should get trim

  23. Fido Authentication- User is not able to authenticate via FIDO in first time, user need to kill app or refresh inorder to register device

Known Bug

  1.  Manager notification : receiving user name required manager name 

  2.  Multi-role assignment with form,then form adding repeatedly for each role, expected only one form should bethere 

  3.  Fido - Push/fido not getting removed from mobile app 

  4.  Password converter only accepted encrypted value . it should also accept user's editable value

**No new features were introduced. This version has implemented all the features and bug fixes from the **

3.0.4

Application Field

Cymmetri Field

Application Field Type

Cymmetri Field Type

Create Only

Update Only

whenCreated

startDate

Ldap DateTime Custom

Datetime

TRUE

FALSE

accountExpires

endDate

Ldap DateTime

Datetime

TRUE

TRUE

thumbnailPhoto

profilePicture

Ldap Byte Array

Array

TRUE

TRUE

3.0.4-Beta

Version: cloud_3.0.4-beta product release

Date: 03 January 2024

**To ensure the highest quality standards, some features in this version are marked for further refinement and will not be included in the current release. Please refer to the next approved release for updates and improvements.**

New Features

  1. Connector

    • Darwinbox

    • SuccessFactor

  2. Cymmetri Verify now supports webauthn QR code scanning from mobile in case mobile camera doesn't support QR scanning

  3. Persistent Form Enhancement

    • Added Form submission support on Role assignment.

    • Added Form submission support on Role unassignment.

    • Added configuration to enable/ isable form submission on role assignment and unassignment.

  4. Policy Map Data Type Converters

    • Added support to input pattern of date of target system.

    • Added support to convert date & date time of target system using mentioned pattern.

  5. PAM

    • Download AD Certificate

  6. Passwordless Login Flow Enhancement.- Now tere is MFA registartion is optional in login

  7. Lock user on mfa failed Attempt.

    • Added configuration for mfaattempt, coooldown period.

Fixes

  1. Reset password OTP- Max limit validation message should be displayed if 3 invalid otp are provided

  2. For the newly created tenant configuration showing error

  3. For newly created tenant notification template not loading

  4. Time-based/Normal Application- When deprovisioning time-based application or successf ully assigned application is going into failed state showing null pointer exception

  5. Selfservice-Behalf-User-Group-Group is already assigned then also it is again available for t he assignment

  6. Selfservice-Team-User-Group-Group is already assigned then also it is again available for t he assignment

  7. Group-Custom Attributes not getting updated in group while assigning user to the group manually

  8. Provision Rule- User need to refresh page when adding/updating application role condition

  9. Recon pull with AD-For default data related to date it is not working

  10. ctrl+K search -add MFA rule not present

  11. Partner portal-Add customer with domain-for domain field validation should be as per the normal registration

  12. Cymmetri verify App(Selfservice(-Need to handle auto register flow in the application MFA

  13. App Auth does not work when verify app in closed state

  14. ios 17.2 Auto Auth not working

  15. ctrl+k search-Read only user redirecting on add form

  16. SAML-Expression-Provide sample on i icon

  17. PAM- Rename server to device

  18. Login with PAM Read Access Admin-PAM>Devices>Setting: User is able to edit complete p age details and showing processing validation message when clicked on save button

  19. User not getting deleted from AD when assign in AD

  20. Recon-Pull-Group, for one user having 900 groups, then under recon history showing error,same vice versa one group multiple users

  21. Take pull from AD- User having remote group present in AD

  22. When password is expired and the user is trying to change password then it is not adhering password policy, accepting same old password

  23. SAML-Regular expression-if user entity not exist and doing SSO then in audit data should be present

  24. Identity Hub- Group: Validation message should be shown when clicked on assign group button

  25. Identity Hub >User: Custom attribute dropdown is not completely visible

  26. Custom Attribute Import- When password attribute is imported via csv file then password should be visible in encrypted form in user details

  27. Custom attribute Import via API EXT- Password should be encrypted form when imported

  28. Application MFA- Showing routes issue when accessing application

  29. Not able to login on partner portal via admin login

  30. Route issue-On click configuration tab

  31. On Behalf- Route issue

  32. Import> Download sample file- showing route error

  33. Browser cookies disable-end user-facing difficulty

  34. Calendar: Resolution specific> Calendar Ul is getting glitched at 75% 80% 90% zoom

  35. Identity Hub-Users: User should not be able to assign application again if already is assigned.

  36. Teams-Add user showing unknown error

  37. Inbox showing unknown error

  38. Teams-User list not showing

  39. Application Recon- When user is trying to Pull users from database and if pin code is blank, then default set value should have been taken

  40. Authentication> Auth rule- Showing Rulesrvc not found validation message

  41. Policy map update-on save showing error

  42. Hide this /disable button when script is enabled

  43. MFA- Rename SMS Authenticator to OTP Verification

  44. Application getting assigned from UI. If it is failed.

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

  3. Workflow initiated for form but form is getting updated without workflow approval.

3.0.12-Beta

Version: cloud_3.0.12-beta product release

Date: 18 April 2024

**To ensure the highest quality standards, some features in this version are marked for further refinement and will not be included in the current release. Please refer to the next approved release for updates and improvements.**

New Features

  1. Upload filename length validation: When file is upload in form of profile image, excel file import then validation is added for the file name length.Implement pages are as follows (20 characters)

    • Selfservice profile picture

    • Application image

    • Excel upload in User import, manager assignment, application assignment, group assignment,Role import

  2. For the remote group, when a user or application is assigned to the group, they will not be assigned to Cymmetri until they have been successfully assigned to the target.

  3. Workflow Config

    • After creating work flow now user redirect to workflow config page.

    • Now we can't active workflow if approver not configure in workflow config.

Fixes

  1. Application> Roles- Add toggle button to Active /Inactive status.

  2. Add application/device name with space,Space should be trim

  3. Users> Activity- Filter and search should be added in user activity

  4. Workflow-"Save" button should remain disabled unless some condition is mentioned

  5. Application SSO-attribute mapping-for duplicate entry,message should be show on same screen,refer other module for the duplicate entry error message

  6. Lifecycle Mgmt>Hook Config - Search filter is not working

  7. Amaya Connector- Show complete name on tooltip

  8. User Setting- Change validation message for all three tasks( Active, Inactive, Delete)

  9. Workflow Configuration- If approver is not present then workflow config should not get active

  10. Partner Portal - Add Asterisk (*) for marked fields

  11. Partner Portal- The validation message indicates that spaces are acceptable, but the field is not currently allowing them

  12. Partner portal- Company name letters should be extended to 100 characters and space at the end should be trimmed

  13. Amaya-Param getting duplicate

  14. Trigger email to user when MFA max attempted in login

  15. Master > Audit logs- Audit for fields created or updated in Master is not showing except for Grade

  16. PAM Device- Not able to search PAM devices from my workspace

  17. Application add with space,Need to handle space in backend also as temporay fix deployed from UI side

  18. Rename- Dynamic json connector to Amaya

  19. Amaya connector- Rename Dynamic Json connector to Amaya

  20. Dynamic Json Connector- Text is overflowing tag border

  21. Delegation- User should not be able to save delegation when start date is in past.

  22. Amaya-policy map-felicity-If for policy map attribute not generated then default value should be there

  23. Add application-For policy map default should be off

  24. Update pagination offset - label and placeholder

  25. Amaya-Response getting hide

  26. Rename Amaya provision sub tab to User Configuration

  27. Amaya-Policy map,tooltip overlap issue

  28. Partner portal-under cymmetri customer total user count showing-1, actual available-12

  29. Recon- Modes should be non editable

  30. Import users via CSV/recon- Users should not be imported/ should show error when particular usertype, department ,designation fields are inactive

  31. Load Test Data: Identity Hub> Users- Pagination is not working when multiple users(Load) are present

  32. Workflow- Workflow popup box is showing unknown but in pending workflow is going into requestor manager

  33. User-Filter with custom attribute not working on below data

  34. AD Application new bundle- If user is inactive in AD, and same user is updated in Cymmetri then user in AD should also get updated

  35. AD Recon push-User not getting push in target (New bundle)

  36. Recon- Timing is not correct

  37. Application delete-Deleted application present under Provision rule ,even after application deleted

  38. Processing please wait message should be changed, when no data is entered and clicked on preview assertion

  39. Deprovision- User is getting suspended when deprovision rule is executed via scheduler when no end date is applied or status is inactive

  40. Reports> Filter- Showing error message to enter start and and date when resetting filter or applying any other filter.

  41. Remote Group assign in bulk-Not moving all user in group under AD

  42. To verify user deleted from AD OU and cymmetri admin trying to assign remote group

  43. AD application - In Suspend user, application status is showing fail updation state

  44. Remote group-bulk assignment showing ServiceUnavailableException

  45. Group-Recon pull-update and full sync assign/update-taking too much time

  46. Ad Application- Application assignment is going in failed state , but deleting application is also getting failed

  47. Assign user to remote group is failed

  48. AD application recon- When workflow is configured and recon is executed, then user is going in pending workflow

  49. AD New Bundle- Thumbanail Photo is reflecting incomplete(In hex form) in AD

  50. Workflow- Workflow popup box is showing unknown but in pending workflow is going into requestor manager

  51. Recon-Name not present then also showing error for the duplicate

  52. AD application - In Suspend user, application status is showing fail updation state 

  53. Custom attribute Import via API EXT- Password should be encrypted form when imported 

  54. SSO-Openid not working on QA, same working on dev 

  55. Multi node-Application assign with role, all user getting assigned but still import showing inprogress 

  56. API ext (API Client) User not getting created 

  57. Deprovision rule-user data not getting updated when change Grace Period 3 to 0 days 

  58. Unable to add Gmail account on Android after logging into Cymmetri 

  59. Tenant specific> Reset OTP config- Not able to save configuration 

  60. Partner portal- Display validation message specifying some fields are missing 

  61. Grade workflow- Preference config popup box is showing user name but pending is showing Unknown 

  62. Group recon pull-when space is in name then not going in ignore case 

  63. Workflow- Sequence for approver is mismatched in preference config popup box and in pending workflow 

  64. Workflow- Workflow in preference popup box is showing user name but in pending showing unknown when applied for user list or grade 

  65. Workflow- When approver is set as reporting manager and application workflow is initiated then preference box is showing approver name but pending is showing unknown 

  66. Schedule report- cron not getting updated, from hourly to change once in day then also report receiving hourly 

  67. creating the user through the JIT Message was rejected due to issue instant expiration 

  68. PAM device is assigned then on access showing message for the disconnected 

  69. AD Adaptor token- Token is showing Invalid 

  70. PAM Device- showing processing plaese wait validation message with 403 forbidden error 

  71. Application- Showing processing please wait validation message. 

  72. Loadtest-workflow page not loading 

  73. Expired session: Showing blank page when clicked on user setting logout tab 

  74. Suspend Config- User should be able to disable suspend config 

  75. Deprovision- Deprovision via scheduler is not working 

  76. AD-Recon pull with update-If user data removed from AD and taking pull,then this data not updating in the cymmetri user data 

  77. group push-not taking user in AD at the time of update 

  78. Daily scheduler running late 

  79. AD Application- Showing error when trying to update profile picture 

  80. MFA- Rename SMS Authenticator to OTP Verification 

  81. Global Auth-When the "Single Session > Block Session" setting is enabled, attempting to log in with the same user account should block the user even before verifying Multi-Factor Authentication (MFA). 

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. Workflow initiated for form but form is getting updated without workflow approval.

  3. In application setting if show to user flag off then also application show in recent application.

  4. Unable to identify application properties data type where value is empty

3.0.7-Beta

Version: cloud_3.0.1-beta product release

Date: 09 February 2024

**To ensure the highest quality standards, some features in this version are marked for further refinement and will not be included in the current release. Please refer to the next approved release for updates and improvements.**

New Features

  1. PAM SUDO SU feature for linux server.(For SUDO SU shortcut key Ctrl+Shift+E)

  2. SAML Assertion Preview

  3. Encrypt saml response

  4. ETL

    • Custom Create user in AD API with unboundid library

    • Custom user assign to group in AD API with unboundid library

  5. Configurable UI Info and Actions:

    1. Hide "Reset / Unlock User"

    2. Hide "Login Help Page Link"

    3. Configure "Login Help Page Link"

    4. Hide "IP Address"

    5. Hide "Self-Service App Links"

  6. Login Help page external link updated

  7. Cymmetri Verify

    1. Firebase version upgradation

    2. A troubleshoot page provided if FCM token is missing

  8. SSO UI migration

  9. Made Gateway IPs and Proxy IPs non mandatory on the Masters -Zone page. Only Name and CIDR fields will be mandatory.

Fixes

  1. Default delegation consents do not convey responsibility of delegator or delegatee

  2. Self service app- On behalf: When clicked on application/groups from dropdown mobile keyboard is getting displayed and due to that applications/ groups visibility is less

  3. Provision rule-On click save showing error,without condition

  4. Configurations-general-config-Rename message for User Decommission Config

  5. Label update for suspend config

  6. Provision Rule; Groups/Application- If user is selecting any local group in first field then second field is greyed out not showing other local groups

  7. Notification content should not be hardcoded

  8. Remove trailing slash from selfservice endpoint

  9. Error handling for product Webhook custom error

  10. Application SSO-attribute mapping-without selecting Cymmetri Attribute save button should not be enable, as this is mandatory field

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

  3. Workflow initiated for form but form is getting updated without workflow approval.

3.1.0 - Product Release

Version: cloud_3.1.0 product release

Date: 02 May 2024

New Features

  1. Add Welcome Guide when no nodes added

  2. Amaya Operations cards messages updated

  3. Tooltip DX enhancements

  4. Add confirmation dialogue when request method is missing

  5. File Upload Validations based on filename length and file size

    • File validation applied on User Bulk Imports, Group Assignments, Application Assignments, Role Imports, Upload metadata SSO.

    • Branding Image upload applied image size validation and image name length valdation.

    • Validation also applied on self service User avatar upload, application icon upload.

  6. Cymmetri Verify App issuer format is changed now so there wont be duplicate record creation from now onwards, earlier we did not take into account of the environment but now we are considering that as well

Fixes

  1. Deprovision Via scheduler when threshold value is set:- Past date user is also getting deprovisioned when rule is applied on status 

  2. Application-Role-One role mandatory, validation should be present at least one active 

  3. Node name without spaces overlap 

  4. Amaya- Not able to drag down node which is at the top most corner 

  5. Campaign - Campaign action reminder email time calculation wrong 

  6. Campaign- Campaign is getting aborted and summary is showing blank when campaign for local group is executed. 

  7. Custom attribute - When custom attribute filter is applied in users, showing no users found 

  8. Workflow- Preference config box is not visible while deprovisioning application 

  9. Self service app: While setting up secret question authentication in mobile app, user need to click twice on question field. 

  10. User activity Ascending Descending not working 

  11. Amaya Connector Recon- Showing duplicate role remarks, but in duplicate field showing 0 records 

  12. Identity Hub- Groups- After editing groups when on application / activity page user is redirected to users page by default

  13. My workspace> Create new tags- showing older suggestion as soon as clicked on new tag field 

  14. AD Application - View attribute is empty 

  15. Tenant registration | Pressing tab key glitches UI 

  16. Missing error code mapping 

  17. Grade Workflow- When workflow preference config is set to visible, and workflow is applied for user creation, then popup box is showing user list but in pending showing unknown instead of user list

  18. Amaya- When the back button is clicked, a save/discard popup box will appear. However, clicking anywhere on the page directly navigates the user away from the operation page. 

  19. Amaya- Save/Discard popup box should not be shown when user is trying to go back without saving any changes 

  20. Mobile app- Secret question- Field is showing required even when data is present in field 

  21. Cymmetri Verify app- Password recovery should be provided for Exported TOTP user files in case user forgets the password 

  22. login via Authenticator-identity provider is inactive then also user able to login. 

  23. syslog-configuration- UDP test, for invalid IP also giving success. 

  24. Unable to have TOTP account for same username on different environments 

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. Workflow initiated for form but form is getting updated without workflow approval.

  3. In application setting if show to user flag off then also application show in recent application.

  4. Unable to identify application properties data type where value is empty

3.0.8-Beta

Version: cloud_3.0.1-beta product release

Date: 23 February 2024

**To ensure the highest quality standards, some features in this version are marked for further refinement and will not be included in the current release. Please refer to the next approved release for updates and improvements.**

New Features

  1. UI/UX Changes:

    • Skeleton loaders - Improved loading indicators

    • Filter enhancement for Users and Application pages - Now filter persists the data once go in the detail page and come back also an indicator to show how many filters or any filters are applied

    • Branding changes - Now the preview of branding will be on scroll for better UX , "should help icon be shown " field would highlight the help icon

  2. Mfa attempt Admin User lock

    1. Mfa attempt config added in global auth policy

    2. Self-unlock flag to unlock the user during admin lock the user

    3. Email for invalid mfa attempt

  3. Service Provider (SP) Initiated SAML Single Logout

  4. Secret Questions verification changed

    • Earlier it used to show all question and mandate user to fill all the configured questions . Now it will only ask user to show dropdown multiple times configured by admin for minimum correct answers.

  5. SBI VAPT :

    1. Encrypt 'login' in some public api same as password encrypted. Following APIs are changed:

      1. validateIdentity api : on login page validateIdentity api change get type to post and in request body login encrypted value pass.

      2. token api : on login page token api login encrypted value pass.

Fixes

  1. API Integration for passwordless flow reset password

  2. Workflow- For user list workflow approver, user is showing in list dropdown but in pending workflow it is showing empty.

  3. Application- Application name should be unique

  4. Applications Group mapping- Change the validation message as only one group can be added in group mapping/ disable the add attribute button after 1st group mapping is done

  5. AD application Recon- When importing users via recon having provision rule assigned for User creation with condition, then showing error in recon history and again after executing run now command then user is getting imported but going in Ignore case.

  6. AD Application recon- When workflow is applied for User creation having condition applied(Department=Accounts), and user is imported via recon, recon history is showing user assigned but when searched In identity hub-Users, showing user not found.

  7. Notification Template- Showing processing please wait message when trying to click toggle button

  8. Provision Rule- User should not be able to save provision rule without adding applications/groups

  9. SBI VAPT || Testing and changes for SBI as well as product

  10. Application SSO- Label change to update

  11. My workspace>Inbox- User details popup box should not be displayed when user is deleted from admin account after initiating workflow

  12. Deprovision- Remove Exclusion Applications field

  13. Delegation account- Change label from Delegate Session Active to Delegate Session Information

  14. Users> Applications- Total number of applications assigned should be shown in user account

  15. User: Menu Action- There should be sync event toggle button while marking user inactive in user menu as available while marking inactive from user setting tab

  16. Policy attribute- When removing policy attribute, that field is not getting removed also it is visible in policy map application field dropdown

  17. Identity Hub> Users- Users should be searched on basis of Usertype as well

  18. User Creation Workflow- When clicked on the cancel button on the workflow preference popup box, it should remain on the user creation page. For now it is cancelling the whole process

  19. Application> SSO>Configuration>Edit configuration- UI for logos and name is not proper

  20. Application SSO> Configuration- Marked button should be disabled until service provider is selected

  21. Branding- Change label as both the fields are sounding similar

  22. Branding- Preview is not available after changing setting

  23. Branding- Add a short note/sample file for default help link when show help button is Yes

  24. User Filter- Reset button should reset all the filters applied and load complete data

  25. Self Service App>Managed access- Fields on right side should be slightly moved to left as in mobile it is not visible properly

  26. Application Audit logs- Applications are getting updated when password reset is performed for users.

  27. Selfservice app-MAX MFA attempt message is not readable

  28. Self Service mobile app: Application- Application Tag is not visible when clicked on move to tag option at first time and later on option is continuously visible

  29. My workspace> Inbox- Starred requests are not getting saved in starred folder

  30. Exclude application > delegation- When any application is added in tag and excluded by delegator, then should not be visible in delegatee account

  31. My workspace: Application- One application should be assigned/moved to one tag only

  32. Teams Configuration- Showing route issue when saving new teams configuration

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

  3. Workflow initiated for form but form is getting updated without workflow approval.

3.1.4-Beta

New Feature

  1. UI/UX || Warning added || Application Config Import Modal || Auto 'Create Only' for User Principal policy mappings

  2. A new feature has been developed for the "Recommendation Engine", enabling seamless integration and management of application and role recommendations. The recommendation engine supports the generation of personalized applications and role suggestions for each user. The system supports the automatic synchronization of data from various sources, ensuring that recommendations are always based on user behavior. All recommendation engine configurations and data synchronization are stored and can be easily retrieved and updated as needed.

  3. UI/UX || Amaya || Add support for JSON body validation through validate button

  4. Audit log comparison for oldObject and newObject when they are in detailed format

  5. UI/UX Inconsistent button placement in some modules fixed to a default below position

  6. UI/UX Onboarding walkthrough of New users

  7. ICICI: a. The inbox title in the workflow setup event has been updated to display the workflow name. b. Workflow (Pending workflow list) requester and requestedFor column added for display

  8. Identity Analytics (Reporting Engine)

  9. End-to-end Request/Response Payload Encryption for all authservice's API. (/authsrvc/*)

  10. User Threshold (Phase 2): i. Update Email Title and Template ii. Create a new 'Move to Archive' button to manually archive a user. iii. Make the notifications field mandatory in the User Threshold Configuration. iv. Added the Org Admin as the default notifier in the user threshold configuration. (Not supported for old tenant). v. Update UI Error Message Format vi. The User Threshold staging mode name has been changed. vii. Failure to Move Staging User to Archive Manually and Audit Log Display for fail. viii. The changes made to the staging dashboard view. Include a comparison between the previous and updated versions of the UI. ix. Show the display name in the Threshold Delete operation on the Staging Dashboard. x. Notification Field in User Threshold Config for deleting users.

Fixes

  1. Amaya- When server connector timeout is changed and test configuration is clicked, it shows a "connector not found in cloud" error in the Audit log

  2. Import User - If loginid already exists, then the remark shows "Usrsrvc.existing Login". Change this text to "Existing Login ID"

  3. Import/Export- Showing host server details when the file is imported for script connector

  4. My Access - Tags - Roles is not getting displayed in the Application

  5. Application - Clicking on the role tile, SSO is happening and also while clicking on close icon, SSO is happening

  6. Applications- When any attribute is updated (made empty in the target application) and recon for both exist operation is executed, the corresponding attribute in Cymmetri should also be cleared

  7. Reports- SSO based application- Reports are blank/ not showing data when SSO based application are accessed (To correct the data need to perform data-logger sync for respective tenant. Refer configuration steps here)

  8. Deprovision- User is getting deprovisioned even after user status is changed to Active from Inactive

  9. User threshold mail notification- Title changes required

  10. Audit log-Recon - When recon is executed with status as Inactive, audit log is showing "Recon initiated successfully" but not any log for execution failed/aborted

  11. Audit Filter- Add cross button in Target Type and Action field.

  12. Threshold Config- Validation message for all three operations should be similar

  13. Threshold Create/Update- Spelling for exceeded is not correct

  14. Notification Template - Toggle and status should display in status column as per other modules.

  15. Create User- While creating user on newly created tenant, assign group page showing text "No group assigned , assign group"

  16. User setting- External idp rule is active-An admin user should not be able to reset user password when the external IDP rule matches the user condition

  17. Create user - While creating user on newly created tenant, assign application page showing text "No data found, add application"

  18. Audit Filter- Add cross button in Target Type and Action field.

  19. Portal-For module update showing error, already exist

  20. My Access - Tags - Roles is not getting displayed in Application

  21. Threshold Config- Validation message for all three operations should be similar

  22. Threshold Create/Update- Spelling for exceeded is not correct

  23. Notification Template - Toggle and status should display in status column as per other modules.

  24. Create User- While creating user on newly created tenant, assign group page showing text "No group assigned , assign group"

  25. Create user - While creating user on newly created tenant, assign application page showing text "No data found, add application"

  26. Group Unassignment: The message appearing on group unassignment is incorrect

  27. Push and FIDO scan zoom functionality not available at the time of Device MFA

  28. Push and FIDO scan zoom functionality not available at the time of application MFA

  29. Campaign Reassign -inactive users are also listed for reassignment on click

  30. Login page- AD auth- Provide proper UI message when AD adapter details are incorrect

  31. Amaya- When server connector timeout is changed and test configuration is clicked, it is showing "connector not found in cloud" error in Audit log

  32. Import User - If loginid already exist , then remark shows "Usrsrvc.existing Login" . Change this text to "Existing Login Id"

  33. User threshold- Pending Staging- When changing page select all box should be unchecked.

  34. Threshold Pending staging- Whenever the page changes or the number of records per page is modified, the selection should be reset

  35. Import/Export- Showing host server details when file is imported for script connector

  36. Threshold pending staging- When the retry button is clicked multiple times, the validation message does not appear after the third click on UI

  37. Application assignment- Change user search suggestion watermark

  38. Onboarding registration- When resolution is at 80%, PAM report admin option is not visible in dropdown

  39. Reports- SSO based application- Reports are blank/ not showing data when SSO based application are accessed

  40. After release v 3.1.2, for old updated tenant campaign module is disabled

  41. Onboarding registration- When an application is selected and then reverted to the previous page, selecting the application again causes the application count to double

  42. External JIT- JIT configuration should be disabled until new external idp configuration details are filled

  43. External IDP- JIT- API is showing "undefined" error on clicking JIT button and on enabling JIT configuration

  44. External IDP- JIT- Reverse the title, it is confusing for user

  45. MFA - Secret Question - Question selection is getting non-selectable after entering incorrect answers and then retrying for correct answer

  46. My workspace>Inbox- Count is not showing when records are in claim

  47. Reports( Employee's with upcoming contract end date) - By default date filter should be applied of 30 days

  48. Provision Rule - Cursor of the condition is getting overlapped with footer of the page.

  49. Onboarding - Login credentials timeout error

  50. My Access - Superset Application logo and label should be changed

  51. Applications- When any attribute is updated (made empty in the target application) and recon for both exist operation is executed, the corresponding attribute in Cymmetri should also be cleared

  52. Deprovision- User is getting deprovisioned even after user status is changed to Active from Inactive

  53. Audit log-Recon - When recon is executed with status as Inactive, audit log is showing "Recon initiated successfully" but not any log for execution failed/aborted

  54. User threshold mail notification- Title changes required

  55. Application- Managed view- When manager is removed from Cymmetri, user is still getting displayed in managed view

  56. Create Threshold Config> Csv import- Showing empty records in pending staging list when threshold limit is exceed and user are imported via csv file

  57. Reports- SSO based application- Reports are blank/ not showing data when SSO based application are accessed

  58. My workspace>Inbox- Count is not showing when records are in claim

  59. login with admin-Campaign detail show role also, currently role showing only for campaign manager

  60. Cymmetri Selfservice App - Once we click on the web link from scanner , it should show confirmation popup on screen (Suggestion)

  61. Selfservice Mobile App - When app is in Quit state and open the app via scanner(camera), it is not redirecting to login page of the website

  62. Push Authenticator - Need to change the error message

  63. User creation- While creating new users then going to next level that is on groups page and then on application page ,then user should be redirected back to the group's page when back button is clicked instead of existing user creation page

  64. Showing error when saving workflow with name( User creation, Application provisioning, Application deprovisioning)

  65. deployment_analytics_1 Service CPU utilisation is 100%

  66. Campaign-email report showing error

  67. Some time tenant registration not working,showing WriteConflict error in the service

  68. Application provisioning and deprovisioning workflow initiated request is not getting displayed in activity logs.

  69. Workflow Rules - Application Deprovisioning event - If condition is set as RegEx for custom attribute is not working

  70. User update-Showing audit failed-Write conflict

  71. Report - Updated record should display on top.

  72. Auth rule showing unknown error

  73. Workflow List - View any workflow detail - While clicking on info icon it is showing Grade List Detail

  74. AD-Recon-If Policy attribute marked inactive then also it is getting pull from AD.

  75. Login via Application admin- When click on application showing processing please wait error message.

  76. Applications- Application are not getting assigned to user and also audit log is not visible for the same

  77. PAM write admin not able to assign users,user list not populating

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. In the application setting if to user flags off then the also application shows in the recent application.

  3. Unable to identify application properties data type where value is empty

  4. Amaya || Create user operation fails due to an invalid password

  5. Reports- Records are displayed after 11min approximately

3.0.11-Beta

Version: cloud_3.0.11-beta product release

Date: 05 April 2024

**To ensure the highest quality standards, some features in this version are marked for further refinement and will not be included in the current release. Please refer to the next approved release for updates and improvements.**

New Features

  1. New Feature - Amaya (Schema Maker): A new feature called "Amaya" is released for generating policy map, policy attribute, and also for generating schema for various functions - Create User, Update User, Sync User, Search User etc. Using a UI-based designer, an administrator may configure JSON REST-API based applications without needing to write scripts for the above mentioned functions.

  2. Role Required in Assign Application(Backend Validation):

    • Bulk Application Assignment

    • Admin Application Assignment

    • Admin User Page

    • Selfservice, User Application Request

    • Selfservice -> Teams, Application Assignment

    • Selfservice -> Onbehalf, Application Assignment

  3. Active Directory new bundle (Using unboundid.ldap.sdk library) <Group operation supports>

    • Added a field inside Active Directory User Configuration Page: "Add or Remove group using Simple AD".

  4. Added a default filter for the start date as the current day in all report detail views.

  5. The view button in the application role is only visible when edit access is not provided to the user, but read access is granted, such as for read-only users.

  6. PAM - Device Termination when device unassigned

Fixes

  1. Inbox- Request count should be shown in claim> open request as visible in Requests>Open request

  2. Application deprovision Workflow- When removing role from user application, workflow is getting triggered but before saving popup box is getting disappeared

  3. Password Policy- Accepting -1 in password history versions and also displaying in policy rule when changing password

  4. Password Policy- Password history versions should have default 0 value and also add note specifying description of 0 value.

  5. Import user with grade,need to handle user import with inactive grade

  6. Attribute setting- Not able to disable grade attribute

  7. Audit log- Showing application id instead of application name when moving application to tag from self service app

  8. AD Authentication- Audit log should be shown when changing password for AD authenticated user

  9. My workspace >Teams>Users- The message "User account locked" appears whenever changing pages.

  10. Forms- Field name is not displaying double spaces when inserted in JSON field

  11. Workflow Config- Add Remove button for stage 1 user

  12. Tenant registration flow- show password not working

  13. Workflow- Pending/ Inbox- Menu action should not be visible for every application or when field is empty.

  14. Identity Hub>User Filters- When applying a filter for inactive users or any other filter and then activating the same user, the filter selection is removed, but the count is still displayed.

  15. Upload CSV- Not able to drag and drop csv files in import users, manager assignments, groups

  16. Global module search-when product is disabled and the user trying to search then showing an error

  17. Application update Workflow- Workflow is not getting trigged when application role is assigned to user

  18. Partner portal-delete customer not working

  19. Applications-For old google applications name getting replaced with Google Workspace

  20. Password Policy>Blacklisted Password- When setting blacklisted password for user showing error

  21. Password less login showing error

  22. Email Notification- User is not receiving email notification

  23. Version Specific > Delegation recent apps- When delegatee is accessing account then excluded application are still showing in recent used apps

  24. Admin MFA -on click save showing error

  25. TEAMS-Menu action click showing unknown error

  26. Admin Dashboard, Risk Dashboard and Insight reports are not loading

  27. Taking time to load data in complete application

  28. User-Activity -taking time to load data

  29. AD- Recon- Push- Users are going into pending state for new AD bundle

  30. Managed View- IDM value is not getting displayed

  31. Notification template-need to add middlename attribute under system variable

  32. Users | Sort by filter should be beside Sort Order

  33. Role mandatory-In import assign application there is no validation, without role also able to assign

  34. Identity Hub>User>Setting- Admin should not be able to lock himself from setting

  35. Suspend user-for AD update , remove application

  36. AD application - In Suspend user, application status is showing fail updation state

  37. Group-Recon pull-update and full sync assign/update-taking too much time

  38. AD Group pull || Only under 1000 member getting pulled (Connid Restriction)

  39. Remote group-bulk assignment showing error, "failureReason" : "javax.naming.ServiceUnavailableException: [LDAP: error code 51 - 0000200E: SvcErr: DSID-031A1202, problem 5001 (BUSY), data 0 ]; remaining name 'CN=allgroup,OU=allgroup,dc=cymmetri,dc=in'"

  40. When Add group pull/push then server getting stuck due to memory increase.

  41. Remote Group assign in bulk-Not moving all user in group under AD

  42. AD Application new bundle- If user is inactive in AD, and same user is updated in Cymmetri then user in AD should also get updated

  43. AD Recon push-User not getting push in target (New bundle)

  44. Adaptive MFA-Blacklisted ip configuration- Not able to enter range

  45. Phone number - Phone number and country code validation issue

  46. Partner portal- Company name letters should be extended to 100 characters and space at the end should be trimmed

  47. Partner Portal- On admin approval dashboard page, column name width should be identical, and if name is extending then extended name should be shown in hover.

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. Workflow initiated for form but form is getting updated without workflow approval.

  3. In application setting if show to user flag off then also application show in recent application.

3.1.5-Beta

New Feature

  1. UI/UX - Workflow Inbox User detail will now have applications detail as well assigned to the user.

  2. UI/UX - Workflow Inbox will have a start date and end date filter

  3. User delete workflow support a. Workflow configuration support b. Rule configuration support

  4. CISO Dashboard - REVERTED

  5. Amaya || General Config-based role data type

Fixes

  1. PAM write admin not able to assign users, user list not populating

  2. Policy map- Empty value are getting saved in policy mapping

  3. Workflow Rule update - View - Created by and updated by fields are empty

  4. Superset - OpenId issue - While doing sso for superset application, it should is getting redirect superset url with error "The request to sign in was denied"

  5. Threshold configuration- Replace could be to can be

  6. Policy Map- When searching in the search box by any attribute, the search should get reset after changing tabs

  7. Onboarding - Login credentials timeout error

  8. Application- When searching user in application, user can be searched by first name, last name, login id but not by First name+lastname

  9. PAM write admin not able to assign users,user list not populating

  10. TOTP-Lookahead window change , on click save button show warning message,

  11. User delete Workflow - Pending Workflow - Application details tab is not present

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. In the application setting if show to user flag off then also application show in recent application.

  3. Unable to identify application properties data type where value is empty

  4. Amaya || Create user operation fails due to invalid password

  5. Reports- Records are getting displayed after 11min approximately

  6. Deprovision Rule executed via Scheduler - Workflow is not getting initiated for the set of users on the basis of status/end date

  7. Workflow List - Getting error " Contact system administrator" on technova tenant

3.0.10-Beta

Version: cloud_3.0.10-beta product release

Date: 21 March 2024

New Features

  1. Addition of Grade as an attribute for users

    • Workflows updated to support grade based approvers

      • Added grade to Pending Workflow Page

      • Added grade to Workflow List Page

    • Added grade for User profile

      • Added grade in create user, update user and user info page

      • Added grade in user info page for Suspended Users and Archived Users

      • Displaying grade in User Details [Assignee Details]

    • Added grade in Attribute Setting

    • Added grade for the policy map [cymmetri policy mapping drop down]

    • Added grade for the bulk import

    • Added grade in Teams Config Page

      • Added grade in create user, update user and user info page

      • Added grade in user info page for Suspended Users and Archived Users

    • Added grade in OnBehalf config for self user

    • Displaying the grade for self user profile

    • Added the grade for the pull/push reconciliation process

    • Added the grade to get the value of the middle name in a user profile

    • Added grade to create the user through apiext

    • Added grade in JIT to create the user -Not working

    • Added grade value on the page that displays the delegatee

  2. Analytics Metabase in the report

    • Configuration of Metabase

    • Metabase Report

  3. __MANAGER__ support in policy map for manager assignment in Active Directory (Target application)

  4. Addition of Middle Name as an attribute for users

    • Added middle name in create user, update user and user info page

    • Added middle name in user info page for Suspended Users and Archived Users

    • Added middle name for User Profile

    • Added middle name to Pending Workflow Page

    • Added middle name to Workflow List Page

    • Displaying middle name in User Details [Assignee Details]

    • Added middle name in Attribute Setting

    • Added middle name for the policy map [cymmetri policy mapping drop down]

    • Added middle name for the bulk import

    • Added middle name in create user, update user and user info page

    • Added middle name in user info page for Suspended Users and Archived Users

    • Added middle name in OnBehalf config for self user

    • Displaying the middle name for self user profile

    • Added the middle name for the pull/push reconciliation process

    • Added the middle name to get the value of the middle name in a user profile

    • Added middle name to create the user through apiext

    • Added middle name in JIT to create the user -Not working

    • Added middle name value on the page that displays the delegatee

  5. Role Required in Application Assigment

    1. In application setting, Role Required flag added.

    2. Application Assignment flag is enabled in the below mentioned pages:

      1. Application assignment page

      2. User page, in application assignment

      3. Self-Service

        1. When user request for application

        2. Teams page, in application assignment

        3. Onbehalf page, in application assignment

Fixes

  1. Application Update Workflow- In inbox user name and Login Id fields are showing empty

  2. Rename application name as shown below should be Google Workspace and not Google Workplace.

  3. Fix typo in application provisioning labels

  4. Preference Workflow config popup box - Add Auto option in dropdown list when workflow approver is set to user list

  5. My access application- Calendar UI is not proper for 90% resolution

  6. Password policy-Show last sync time if already sync

  7. MFA attempt configuration-take confirmation on save

  8. JIT-Detail showing route error

  9. JIT-Custom field-Only type=USER should be present in dropdown, currently showing group also

  10. correct notification template-login failed

  11. Unlock User- API is getting called twice and login should be shown in encrypted form

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

  3. Workflow initiated for form but form is getting updated without workflow approval.

  4. In application setting if show to user flag off then also application show in recent application.

  5. Creating the user through the JIT: Message was rejected due to issue instant expiration

3.1.2 - Product Release

New Features

  1. The workflow self-approval module was updated to support custom attributes (type: user type and Converter Type: String ) as condition parameters.

  2. Teams config module updated to support custom attribute (type: user type and Converter Type: String ) as condition parameter.

  3. On behalf module updated to support the custom attribute (type: user type and Converter Type: String ) as a condition parameter.

  4. Auth Rule module updated to support custom attribute (type: user type and Converter Type: String ) as condition parameter.

  5. Quick Setup - Setup applications using pre-defined operations

  6. Import-Export App Configuration - Transfer configurations of applications smoothly between tenants, simplifying the setup for users by ensuring all configurations, including user configurations, server configurations, and policy maps, are accurately migrated.

  7. Removal of Deprovision Rule Exclusion Applications Field: a) Manual Execute Deprovisioning b) Deprovisioning via Scheduler c) Update Threshold Delete Config d) Deprovision Rule Updation e) Backward Compatibility f) Suspend or Resume User g) Impact on UI

  8. Access review reject process updated, on rejection workflow support added.

  9. SAML Single Logout

  10. The new screen will show loading on UI till tenant creation is completed once OTP is verified

  11. Interchanged position of login ID and email on add/edit user for better UX.

  12. Add support for the page number field for pagination in Amaya

  13. 360 Recon

  14. Lotus Notes Connector

  15. Application Policy Map (Active Directory) samAccountName is compulsory for Create only flag in User as well as Group (AD application new bundle - When SAMaccount name is set to false in Group policy map, members are not assigned in group when recon Pull is executed for both exist=Update).

  16. Added Warning information and warning popups (Only UI changes no impact on backend functionality): a. Creation of user manually. b. Updating of user manually. c. Bulk upload CSV (creation of user) d. Manager assignment e. Policy map creation and updation f. Reconciliation Pull operation g. Reconciliation push operation h. Selfservice ➝ Teams: i. Creation of user ii. Updation of user

  17. Removal of Email validation from the backend

Fixes

  1. The user info page crashed while the user edit fails

  2. Import/Export of App Configuration

  3. Amaya- Detailed description of failed/executed logs should be shown

  4. AD application new bundle- The group link attribute in the db is empty, and users are not getting updated in the group

  5. AD policy map- Spaces should be trimmed automatically if included while creating a policy attribute

  6. Tenant creation not working

  7. New tenant Registration- Showing subscription end for tenant which is not even registered completely

  8. Secret question configuration- Admin user should be able to delete secret questions when not in use

  9. Secret Question- When a question is already in use and the user trying to delete a question then it should not display a successful delete message.

  10. Secret question- Displaying removal validation message when editing a question

  11. User> Activity- Add a cross (x) button to clear the selection

  12. Onbehalf Config - If the Description is kept blank, no error message is getting displayed on the screen while saving.

  13. Team Config - If the Description is kept blank, no error message is getting displayed on the screen while saving.

  14. On Behalf config- When the view button is clicked, the user is still able to check or uncheck the boxes.

  15. Custom attribute- Even when a custom attribute is disabled from the configuration, it remains visible in the policy map selected dropdown menu

  16. Users - View User- Custom attribute fields text UI is breaking

  17. Custom Attribute- Require text change in success message to " Custom Attribute activated successfully"

  18. Edit User - After deactivating the already assigned custom attribute, in edit user, the system is showing info XYZz" attribute is inactive for the active custom attribute also.

  19. Identity Hub- When clicking on edit info from the user menu action, the user account edit page should open instead of the user display page.

  20. CTRL+K: When any feature/module is already opened and the user presses the ctrl +k button from the keyboard then the search filter modal is opened at the back

  21. Delegation - Delegator and Delegatee consent should not get updated if the user has already set some other consent.

  22. Users> Group- Rename the label from 'Delete' to 'Unassign'.

  23. Audit- Logs for deprovisioned users are getting repeated.

  24. Custom Field- Policy Map- Date is not showing in the correct format

  25. Mobile app- When clicking on the user name for the first time after killing the app, the keyboard is hidden

  26. Custom Attribute-Provision- When a custom attribute with special characters is created and applied in a provision rule (for user creation), the provision rule fails to trigger after the user is created.

  27. Global search (Ctrl+K) - even if characters are not matching still shows suggestions

  28. User setting- An error message should be shown when any action is performed and when landing/refreshing the settings page

  29. Cymmetri Selfservice App - Need to change the message showing in the popup screen while TOTP is getting authenticated.

  30. Mozilla Browser specific- User getting stuck when password-less Webauthn is On

  31. Application - SSO - While clicking on Preview assertion, getting the error "processing please wait"

  32. Product menu getting hidden on workflow page: a. Menu action- Displaying an error message when a user already has one role assigned and tries to assign a menu action.

  33. The user info page crashed while the user edit fails

  34. Import/Export- Showing error message when importing the file into a new tenant (AD specific)

  35. Custom Attribute-Provision- When a custom attribute with special characters is created and applied in a provision rule (for user creation), the provision rule fails to trigger after the user is created.

  36. Quick setup- Data is not getting reset after closing the policy mapping popup box, but getting reset when clicking on the "I'll do later button"

  37. Add Page Number support for Amaya.

  38. Application - SSO While saving the same config in two applications, while clicking on Edit SP config, a popup showing do you want to continue editing the SP configuration? but only the continue button is given

  39. Application - SSO - While saving the configuration in a new application, the save button loader is loading continuously

  40. 360 recon-Hide runnow button from detail view

  41. 360 recon dashboard filter-add dropdown for break type

  42. 360 recon dashboard-label change account overdue to account overdue in the target (also add some info on i icon what is this)

  43. 360 recon-Already running recon need to handle, disable the play button, or show a message

  44. 360 dashboard-make label consistent

  45. 360 recon dashboard-action details showing blank

  46. 360 Degree recon-For execution showing error

  47. 360 Degree Recon- History some time loading some time not

  48. Recon 360 recon- A validation message for missing data is not required as it already shows no data found on the page when recon is not executed at all

  49. 360 recon dashboard-action details showing blank

  50. 360 dashboard-Search not working on break type

  51. 360dashboard-loginid filter not working

  52. 360 recon detail data showing mismatch

  53. 360 recon execute audit log not present

  54. 360 recon dashboard-on 2nd run details getting repeated

  55. Amaya Azure- Showing route issue error message

  56. Import Application- UI for the name is not proper

  57. Import/Export- Recon is not working for AD's new application bundle

  58. Teams config - while removing the condition in Group condition, shows the error " Please try again"

  59. On Behalf config - while removing the condition in Group condition, shows the error " Please try again"

  60. Teams Config - If the condition is kept blank and save is clicked, getting the error " Please try again"

  61. On behalf config- If the condition is kept blank and save is clicked, getting the error " Please try again"

  62. Import/Export Application- Convertor field types in the policy map are not getting imported

  63. Import/Export - When any application configuration is imported into a new tenant, the user should be redirected to the application provisioning page after the upload

  64. Import application- Showing an error message when importing an Amaya-based application if the exported application was without the policy map checked

  65. Amaya- Policy Map Password attribute datatype identified as password instead of string

  66. Amaya- Rename all operations(Test, Search, Sync, etc....) in sentence case

  67. Workflow- Even after updating Grade as the 2nd level approver in the workflow, the 1st level approver is still being set at level 2

  68. Workflow- After updating the user list as the 2nd level approver in the workflow, the 1st level approver is still being set at level 2

  69. Workflow- When the level 3 approver is updated in the workflow, a 'Workflow Not in Range' error message is displayed.

  70. Workflow- Even after updating the reporting manager as the 2nd level approver in the workflow, the 1st level approver is still being set at level 2

  71. Workflow- When workflow over workflow is applied 2nd level approver is not getting updated

  72. 360 recon should consider full sync

  73. 360 recon fails then that 360 recon should be abort

  74. Amaya Felicity Role assignment- Taking time to provide an error message

  75. Deprovision- Exclusion Application- Application going in pending deletion state when that particular application is added in exclusion application while manually deleting a user from the Identity hub

  76. 360 Recon sync with bulk data showing heap size issue

  77. AD new application- User list is not getting displayed showing urersrvc unknown error.

  78. My workspace> Inbox- When workflow assignment is reassigned by admin, then the previous approver should not be able to accept or reject the request if the page is already open in the previous approver account.

  79. Inbox - Workflow Request for setup for application - Need to enhance the details as per user interface.

  80. Error in the server log-authsrvc , No impact on the functional flow

  81. After the campaign workflow triggered on revoked, even though the campaign had ended and the workflow was approved, applications were still getting unassigned.

  82. Campaign - Reviewer can approve self review request

  83. The campaign not getting end, for tenant 2711

  84. Workflow TAT- Workflow is getting aborted when grade is set at second level approver and set TAT time is over

  85. Workflow TAT- Workflow is getting aborted when 2 level approver is set and set TAT time is over

  86. Workflow TAT- Workflow is getting aborted when workflow approver is assigned to the user list

  87. Workflow TAT- Showing error when the user is not present and TAT is over

  88. Workflow TAT- Showing unauthorized error when TAT is over and operation is getting aborted

  89. Recon pull- with both existing links, audit detail not showing

  90. Workflow rule configuration-on edit workflow, previously selected role getting save

  91. AD new bundle- Managed View- View should be proper while separating multiple OU in proxy addresses

  92. AD new bundle- Manager and account expiry is not visible in the Managed view

  93. AD new bundle- managed view- Value is not displayed in a proper format in Name in managed view

  94. AD new bundle- Managed View- Showing different Start time/created time

  95. In the User creation workflow, L1 - User List approved, L2 - reporting manager after TAT is expired, the request is not getting auto reject.

  96. Pending Workflow List - If the approver is User list and Grade then it should display in Current Assign in the pending list

  97. User Workflow - If the reporting manager is set as 2 level approver, the reporting manager is showing as Unknown

  98. Policy Map- When the attribute is searched via the search button and that attribute is deleted then other attributes are not loaded

  99. Profile Picture- After clicking once on the upload button, that button should be disabled

  100. PAM-Server access not getting terminated even after time ends (Related to HA environment only)

  101. User - Assign Application - Workflow initiated - Workflow Approvals page displays User list in Grade type

  102. Pending Workflow -If the L1 approver is User List, then while clicking on the info icon, the popup does not show the user list. Also, it is " Grade List Details"

  103. PAM-Server access not getting terminated even after time ends (Related to HA environment only)

  104. Workflow Rule - Workflow is initiated when the group is set as an approver, the group is not visible on the popup screen

  105. AD new bundle>Group- When the "Sam account name" update checkbox is unchecked and the user attempts to update the description, the description does not get updated in the AD

  106. deployment_analytics_1 Service CPU utilization is 100%

  107. Import/ Export- When a file is exported from a different env (Dev) and imported to QA env, then credentials are also imported along

  108. Security Bug Fixes:- E2E request/response payload encryption for all APIs of authservice (as of now, planning to rollout for all the services in the next phase)

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. Unable to identify application properties data type where value is empty

  3. Amaya || Create user operation fails due to an invalid password

  4. In forgot password/password breach condition-asking disabled MFA factor also

  5. Amaya-Autofill policy map, When the value is not present to the user at the time of application then Amaya passes "$." to the target

  6. Campaign - Reviewer can approve self review request

  7. After the campaign workflow was triggered on revoked, even though the campaign had ended and the workflow was approved, applications were still getting unassigned.

  8. Remote Group- AD Application- When users are removed from a remote group in Cymmetri, those members should also be removed from the group in the Active Directory

  9. Amaya- Client ID should be visible in encrypted form

  10. Provision Rule - While creating and configuring the custom attribute as "New ", the system is not initiating the rule.

  11. AD new bundle- When an AD application is assigned to a remote group, the application is highlighted in the background while assigning but disappears as soon as the application popup box is closed

  12. Reports- When the report is scheduled, Scheduler history shows content not found and the execution status is aborted.

  13. AD Application- When the Ad test provision fails, and the user tries to delete the application from a user account, then the application should gointon a fail deletion state

  14. Audit- Taking time to load audit logs

  15. AD Application- Showing error when inserting start date in AD

  16. In the application setting to user flags off then the also application shows in the recent application.

  17. User lock- When a user account is active, and the same account is logged in through another browser, and by any means, the account gets locked, the first session should get terminated.

  18. Branding- When show Unlock link from branding is kept as No, and the admin user account gets locked, then the user is not able to unlock the account from the login page

  19. Application- When a user is adding /removing a role then it is not getting reflected without refreshing

  20. group push-not taking user in AD at the time of update

  21. Passwordless- WebAuthn; Showing not allowed error

  22. Delegation-On behalf: when login by the delegate and the on-behalf condition is not satisfied still shows the on-behalf toggle button and gets removed when refreshed

  23. AD Application- Group name should not accept space while creating or updating group name

  24. Audit- Audi log should show log when the user is not getting any records in Recon history but showing task executed

3.1.1-Beta

New Features

  1. Framework Upgrade: Java-based services are updated for spring framework, spring boot, and updated utility libraries. Please note it may impact several functionalities: a. Access Review b. Risk Engine c. Data Logger d. Reports e. Webhook Sample

  2. Provision rule module updated to support (type: user type and Converter Type: String ) custom attributes as condition parameters.

  3. Support added for address1 and address2 field in user for the following: a) User Import via CSV File b) Reconciliation Application c) Amaya Application d) JIT e) Workflow - Inbox > user details, should address fields be visible Pending workflow > user details, should address fields be visible Archive > user details, should address fields be visible f) In the SSO profile mapping drop-down these fields should be visible.

  4. Workflow: a. Menu Action: Update the topic of the workflow request for menu action. b. My Request: In My Workspace ➝ Inbox ➝ My Request, we show a list of requests that are requested for logged-in users. Now we provide support to show a list of requests which is requested by logged-in users. So now we are showing both requests which are requested and requests for logged-in users.

  5. 360 Degree Reconciliation: a. Migrated APIs from Python to Java, since it was a major roadblock for performance.

  6. Webhook sample API details a. Added remark of appId in URL

  7. UI improvement - Global search bar (ctrl + k) search result improvement

  8. Screenshot Removed right side panel in my workspace dashboard which previously showed no. of pending workflow requests with the user

  9. Cymmetri Verify App - A sync service will run to check the pending notification actions that did not take place because the app was in a closed-on-background state and will sync the data based on the notifications

  10. Cymmetri Self-Service App - Earlier to register a tenant in cymmetri self-service we used to scan from our app to register a tenant but now you can use any camera or any scanner of that sort to register a tenant

  11. UI Improvement - "Test Connection" should be prevented when an operation is not configured

  12. SLO- Reverted as business case gap in the developed feature

  13. Breached Password (Pwned Password 98crores+) Integration with Password policy.

  14. Common adaptive data moved to master db: a. ipreputation b. short-lived domain c. breached password

  15. MFA: Encrypt userName(login) in the request of API user behavior initiateKeystrokeCheck.

  16. Suspend Resume: a. After the resume of the user's end date is clear and the user acts as a fresh user

Fixes

  1. PAM Workflow- Meta condition workflow for devices is not getting triggered.

  2. The dashboard count is mismatched.

  3. Policy Map- Cymmetri field dropdown should contain Address1 and Address2 fields

  4. Autofill API sorts in alphabetic order for JSON objects for create/update

  5. Onboarding || User should be able to unselect an application

  6. Add and Edit password policy-need to g\show exact labels for the fields

  7. Identity hub>User create- When importing users space should get eliminated

  8. ServiceNow CURL Import not working

  9. "Test Connection" should be prevented when an operation is not configured

  10. TEAMS-Users profile pic not showing

  11. My workspace- Teams- Showing processing please wait validation message

  12. creating the user through the JIT Message was rejected due to the issue of instant expiration

  13. Campaign- The Google Workspace application name is not visible in the campaign

  14. AD application New bundle- Showing error while importing group having special symbol(-) for recon

  15. Application recon pull configuration-recon pull configuration vanished suddenly

  16. login with domain admin-need to provide Adaptive menu access

  17. AD recon user push- When recon is executed in exist on Cymmetri and does not exist in target = Unlink, the operation should have been executed in Ignore case

  18. AD Application new bundle- Group recon pull operation is showing in ignore state but still, groups are imported in Cymmetri

  19. AD New Bundle>Address Field- Not able to add AD application when address fields are mapped, showing error

  20. AD new bundle- When an AD application is assigned to a remote group, the application is highlighted

  21. Cymmetri Verify App - While deleting the account from Cymmetri authenticator, TOTP is not getting

  22. Custom attribute- Even when a custom attribute is disabled from the configuration, it remains visible

  23. Cymmetri Verify App- For old tenants before env was considered if that totp is used for auto-verified

  24. Custom Attribute-Provision- When a custom attribute with special characters is created and applied

  25. Grade workflow- When workflow over workflow is assigned and is approved by the approver, still workflow is still not updated

  26. Cymmetri Self-service App - Once we click on the web link from the scanner, it should show confirmation

  27. Self-service Mobile App - When an app is in a Quit state and the app is via a scanner(camera), it is not redirected to the login page of the website

  28. JIT- Once the default value is set, the user is unable to edit it, and when attempting to edit, the default toggle is shown as disabled

  29. API SSO- Profile mapping configuration is not working

  30. Provision Rule - Custom Attribute - Value field is not accepting space

  31. AD Application New bundle- The "Application assigned successfully" message should not be shown when the test provision has failed and the application is assigned to a remote group

  32. Azure authorization curl is mis-imported

  33. Provision Rule - The existing rule configuration with the custom attribute is not working.

  34. Audit log-for-date filter add default date is Today

  35. User import-file size upload issue

  36. Cymmetri Verify App - While deleting the account from Cymmetri authenticator, TOTP is not getting removed automatically

  37. Cymmetri Verify App - While authenticating automatically via cymmetri authenticator, the "user not found" message comes twice in the iOS device.

  38. Cymmetri Verify App- For old tenants before env was considered if that totp is used for auto verification it shows the user has not found the need to add that compatibility as well, via Passwordless (TOTP)

  39. AD authentication- Showing invalid token error

  40. Tenant creation not working

  41. MFA- Factors showing empty

  42. Breach password- Asking webauth, this factor is only for passwordless

  43. MFA- The user, is not able to login when the user is trying to login using the normal password flow

  44. Teams config- When the team configuration is inactive or does not match the conditions, an error message is displayed after logging in from the user account, yet all data is still shown

  45. Adaptive service responding slow in load testing

  46. AD Application new bundle- When the Unassign/Deprovision reconciliation is executed for group pull/push, the group should not be deleted from Active Directory

  47. Provision rule - The application is not getting configured for the second condition present in the OR condition

  48. SAML- Showing saml type mismatch error when the user is trying to click on Gmail via SP-initiated process

  49. when the user creates via JIT then the user creation workflow should be skipped

  50. PAM-Vaulting Configuration-AD test showing route issue

  51. Login page- The user is not able to login when MFA is enabled( Prod issue)

  52. Reports- When the report is scheduled, Scheduler history shows content not found and the execution status is aborted

  53. AD Application new Bundle- Audit log for pending records should be shown when executing recon user push for failed provision test

  54. Grade workflow- When workflow over workflow is assigned and is approved by the approver, still workflow is still not updated

  55. Time-based application- Scheduler is executed even when a user is moved to suspended

  56. Workflow- User creation using JIT(external IDP Azure)- Workflow is not getting triggered

  57. Password policy- password rule updated with contains instead of exact match

  58. Self-service-My request takes time to load if more data present

  59. Teams config- When the team configuration is inactive or does not match the conditions, an error message is displayed after logging in from the user account, yet all data is still shown

  60. FIDO-On push approve showing message something went wrong

  61. User lock- When a user account is active, and the same account is logged in through another browser, and by any means, the account gets locked, the first session should get terminated.

  62. Workflow Application Deprovision- Workflow is applied for (Role1) but when removing role 2 still workflow is getting initiated.

  63. JIT- Once the default value is set, the user is unable to edit it, and when attempting to edit, the default toggle is shown as disabled

  64. Recon Group PUSH- When recon is executed for both existing Deprovision, then the group should be deleted from the Target application and not from Cymmetri

  65. PAM-Add/Edit vault user showing error

  66. MFA push location showing unknown

  67. /mfasrvc/userbehaviour/initiateKeystrokeCheck in this API login going in plain text expected encrypted.

  68. MFA- Factors showing empty

  69. AD New Bundle- Available Records should be synced when recon is executed for the first time after executing recon in the ignore case

  70. Audit- Change archive to Suspend when user is deleted and moved to suspend users

  71. AD application new bundle - When SAMaccount name is set to false in the Group policy map, members are not assigned in the group when recon Pull is executed for both exist=Update

  72. Recon Group PUSH- When recon is executed for both existing Deprovision, then the group should be deleted from the Target application and not from Cymmetri

  73. Identity Hub-Group- Change Audit log message

  74. AD Application- When the group is unassigned via recon, users, and applications are deleted but the group is not

  75. File Uploads, Filename length validation should be inclusive of the file name and extensions

  76. User import-file size upload issue

  77. AD Recon group Push- When recon is executed for a group that exists in Cymmetri and does not exist in the target system Operation should be shown in Ignore case as no action is performed on Groups

  78. Remote Group- When the user is added to the remote group, the count should be increased automatically or after changing tabs

  79. Recon Push Users- Multiple entries for the same users are visible in Recon History.

  80. MFA- When push authentication is enabled and MFA rules are saved, but then Push auth is disabled from MFA factors, users are still prompted for push authentication when attempting to log in

  81. Deprovision: After resuming a user from the suspended user list and applying deprovisioning via a scheduler with no end date, the user is still being deprovisioned again

  82. Workflow metacondition- The Metacondition name is getting reset after selecting

  83. AD group attribute- When the member attribute is clicked, it redirects to the assignment page

  84. While creating the custom attribute with the same name as the provision rule options, the application is not getting assigned

  85. External IDP Rule- When the external IDP authentication rule condition matches the user details, the user is unable to log in to the external IDP. Additionally, when that user is locked, an 'Invalid Auth Config' error message is shown.

  86. Provision Rule - Custom Attribute - If the list of custom attributes is more than 10 records while selecting and saving the 11 key, it is not getting saved

  87. When the user deletes, add more information in the audit log under the event attribute

  88. Amaya-On update token screen getting blank

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. In the application setting if to user flag is off then the also application shows in the recent application.

  3. Unable to identify application properties data type where value is empty

3.1.7 - Product Release

New Features

  1. Due to the limited resources in QA env and to ensure effective utilization, we are not currently proceeding with the new development to the recommendation service from both the backend and UI at this time. Hence, we kindly request you to exclude the recommendationsrvc service from the QA environment during deployment until further notice.

  2. CISO Dashboard service deployment remains the same as the last release since the sprint release for the same is mid-next week. (EoM - September 2024)

  3. Reconciliation Enhancement a. Reconciliation Job Notifications b. Reconciliation Job Dashboard c. Handling of Partial Job Failures d. Reconciliation Filters

  4. Email Configuration Update a) Mail Username and Password fields no longer require validation, allowing them to be empty. This is because some email servers do not require authentication. b) Other fields, such as Mail Port, Mail Host, and Mail Sender, still require validation to ensure proper email functionality

Fixes

  1. Form logic-When TAT is executed then in the detail show the message "Form Logic Workflow Rejected by system"

  2. Assign Application- The application page not getting refreshed automatically after deleting/assigning applications.

  3. Amaya Policy Mapping- The search button should be present.

  4. Amaya || Validation prevents the usage of variables in the URL

  5. FormLogic || Step 2 of form || Form config JSON should be mandatory

  6. Amaya- The present header key disappeared when saving the value

  7. Quick setup policy mapping- When any fields are not filled and an error is shown, the user should be taken to the error field

  8. Amaya>Policy Mapping- Showing repeated validation message on UI when clicking on the reset button

  9. Amaya- When the JSON body type is changed from raw to any other format, the previous type is cleared, but the response is not being updated accordingly

  10. Amaya- After 3-4 attempts of clicking the validate/save button, the validation message is no longer being displayed.

  11. Form logic-form detail-Need to provide rule link.

  12. Staging Users - Version History - Change the text "Update Version" to "Updated Version"

  13. Form logic-When TAT is executed then in the detail show the message "Form Logic Workflow Rejected by system"

  14. Onboarding- The page is being skipped when the "Create User" popup box is clicked outside of it.

  15. Audit log- UI layout is getting distorted for long role name

  16. Application role- The Role page layout is getting distorted when a role with a long name is created

  17. Application Role- When a role with a long name, including spaces, is created, the UI (specifically the Cancel and Save buttons) is affected while unassigning the role from a user account.

  18. Application Role- UI is getting impacted.

  19. Selfservice mobile app-inbox-User detail not showing.

  20. CSV Bulk Import- When a bulk file is imported via CSV, attribute fields take time to load

  21. Amaya Policy Mapping- The search button should be present.

  22. Workflow || Additional Form Info || Readonly text-based form submissions

  23. Policy map- Empty values are getting saved in the policy mapping

  24. Amaya- When the JSON body type is changed from raw to any other format, the previous type is cleared, but the response is not being updated accordingly

  25. UI new user walkthrough- Sentence correction needed

  26. UI new user walkthrough- Description should be changed

  27. Quick setup policy mapping- When any fields are not filled and an error is shown, the user should be taken to the error field

  28. Amaya- After 3-4 attempts of clicking the validate/save button, the validation message is no longer being displayed.

  29. Form logic-Form table-sorting not working

  30. Form logic-Pre and post hook should be nonmandatory

  31. Form logic-User submissions-Provide date filter

  32. Form logic-on all screen search only works for the exact case, expected should work for matching cases.

  33. Partner portal-add user-country list not loading.

  34. CSV Bulk Import- When a bulk file is imported via CSV, attribute fields are taking time to load.

  35. Form details UI is different in Pending and Completed Workflow than showing in the selfservice inbox section.

  36. Form logic-Selfservice app-My Requests-form detail not showing

  37. Skip Password Expiry- Session expires when the refresh button is clicked having skip password expiry enabled

  38. FormLogic || Unable to save rule after changing condition

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. In the application setting if to user flag is off then the also application shows in the recent application.

  3. Unable to identify application properties data type where value is empty

  4. Amaya || Create user operation fails due to an invalid password

  5. Reports- Records are displayed after 11min approximately

  6. Deprovision Rule executed via Scheduler - Workflow is not getting initiated for the set of users based on status/end date

  7. Workflow List - Getting error " Contact system administrator" on technova tenant

  8. FormLogic || Step 2 of form || Form config JSON should be mandatory

  9. Recon - Abort sync state - System is getting auto abort and failure log showing nothing and

  10. Recon Dashboard History> Search field- A Placeholder should be added specifying search is applicable for only the application name, also No data found should be shown and pagination should get clear when the page is empty

  11. Recon Failure sync status - Showing "Reconciliation In Progress" in fail status

  12. Application Recon History- Slider should be added at the bottom

  13. Recon Dashboard history- Users/groups are getting created in Cymmetri even when the process is aborted from the dashboard

3.1.x Consolidated

(3.1.0 - 3.1.6)

VERSION
New Features
Fixes
Known Bug

3.1.0 Beta (02 May 2024)

  1. Add a Welcome Guide when no nodes are added

  2. Amaya Operations cards messages updated

  3. Tooltip DX enhancements

  4. Add confirmation dialogue when the request method is missing

  5. File Upload Validations based on filename length and file size: File validation applied on User Bulk Imports, Group Assignments, Application Assignments, Role Imports, and Upload metadata SSO. Branding Image upload applied image size validation and image name length validation. Validation is also applied on self-service User avatar upload and application icon upload.

  6. Cymmetri Verify App issuer format is changed now so there wont be duplicate record creation from now onwards, earlier we did not take into account of the environment but now we are considering that as well

  1. Deprovision Via scheduler when threshold value is set:- Past date user is also getting deprovisioned when rule is applied on status 

  2. Application-Role-One role mandatory, validation should be present at least one active 

  3. Node name without spaces overlap

  4. Amaya- Not able to drag down node which is at the top most corner 

  5. Campaign - Campaign action reminder email time calculation wrong

  6. Campaign- Campaign is getting aborted and summary is showing blank when campaign for local group is executed. 

  7. Custom attribute - When custom attribute filter is applied in users, showing no users found 

  8. Workflow- Preference config box is not visible while deprovisioning application 

  9. Self service app: While setting up secret question authentication in mobile app, user need to click twice on question field. 

  10. User activity Ascending Descending not working 

  11. Amaya Connector Recon- Showing duplicate role remarks, but in duplicate field showing 0 records

  12. Identity Hub- Groups- After editing groups when on application / activity page user is redirected to users page by default

  13. My workspace> Create new tags- showing older suggestion as soon as clicked on new tag field 

  14. AD Application - View attribute is empty

  15. Tenant registration | Pressing tab key glitches UI

  16. Missing error code mapping

  17. Grade Workflow- When workflow preference config is set to visible, and workflow is applied for user creation, then popup box is showing user list but in pending showing unknown instead of user list

  18. Amaya- When the back button is clicked, a save/discard popup box will appear. However, clicking anywhere on the page directly navigates the user away from the operation page.

  19. Amaya - Save/Discard popup box should not be shown when user is trying to go back without saving any changes.

  20. Mobile app- Secret question- Field is showing required even when data is present in field

  21. Cymmetri Verify app- Password recovery should be provided for Exported TOTP user files in case user forgets the password

  22. login via Authenticator-identity provider is inactive then also user able to login.

  23. syslog-configuration- UDP test, for invalid IP also giving success.  Unable to have TOTP account for same username on different environments .

  1. Manager notification: receiving user name required manager name

  2. Workflow initiated for form but form is getting updated without workflow approval.

  3. In application setting if show to user flag off then also application show in recent application.

  4. Unable to identify application properties data type where value is em

VERSION
New Features
Fixes
Known Bugs

3.1.2 Beta (26 July 2024)

  1. Workflow self-approval module updated to support custom attribute (type :user type and Converter Type: String ) as condition parameter.

  2. Teams config module updated to support custom attribute (type :user type and Converter Type: String ) as condition parameter.

  3. On behalf module updated to support custom attribute (type :user type and Converter Type: String ) as condition parameter.

  4. Auth Rule module updated to support custom attribute (type :user type and Converter Type: String ) as condition parameter.

  5. Quick Setup - Setup applications using pre-defined operations

  6. Import-Export App Configuration - Transfer configurations of application smoothly between tenants, simplifying the setup for users by ensuring all configuration, including user configurations, server configurations, and policy maps, are accurately migrated.

  7. Removal of Deprovision Rule Exclusion Applications Field: a) Manual Execute Deprovisioning b) Deprovisioning via Scheduler c) Update Threshold Delete Config d) Deprovision Rule Updation e) Backward Compatibility f) Suspend or Resume User g) Impact on UI

  8. Access review reject process updated, on rejection workflow support added.

  9. SAML Single Logout

  10. New screen that will show loading on UI till tenant creation is completed once OTP is verified

  11. Interchanged position of login id and email on add/edit user for better UX.

  12. Add support for page number field for pagination in Amaya

  13. 360 Recon

  14. Lotus Notes Connector

  15. Application Policy Map (Active Directory) samAccountName is compulsary for Create only flag in User as well as Group (AD application new bundle - When SAMaccount name is set to false in Group policy map, members are not assigned in group when recon Pull is executed for both exist=Update).

  16. Added Warning information and warning popups (Only UI changes no impact on backend functionality): a. Creation of user manually. b. Updation of user manually. c. Bulk upload csv (creation of user) d. Manager assignment e. Policy map creation and updation f. Reconciliation Pull operation g. Reconciliation push operation h. Selfservice ➝ Teams: i. Creation of user ii. Updation of user

  17. Removal of Email validation from backend

  1. User info page gets crashed while user edit fails

  2. Import/Export of App Configuration

  3. Amaya- Detailed description of failed/executed logs should be shown

  4. AD application new bundle- Group link attribute in db is empty, users are not getting updated in group

  5. AD policy map- Spaces should be trimmed automatically if included while creating a policy attribute

  6. Tenant creation not working

  7. New tenant Registration- Showing subscription end for tenant which is not even registered completely

  8. Secret question configuration- Admin user should be able to delete secret question when not in use

  9. Secret Question-When a question is already in use and user trying to delete question then it should not display successful delete message

  10. Secret question- Displaying removal validation message when editing a question

  11. User> Activity- Add cross (x) button to clear the selection

  12. Onbehalf Config - If Description is kept blank , no error message is getting displayed on screen while saving.

  13. Team Config - If Description is kept blank , no error message is getting displayed on screen while saving.

  14. On Behalf config- When the view button is clicked, the user is still able to check or uncheck the boxes

  15. Custom attribute- Even when a custom attribute is disabled from the configuration, it remains visible in the policy map selected dropdown menu

  16. Users - View User- Custom attribute fields text UI is breaking

  17. Custom Attribute- Require text change in success message to " Custom Attribute activated successfully"

  18. Edit User - After deactivating the already assigned custom attribute, in edit user , system is showing info "xyz" attribute is inactive for active custom attribute also.

  19. Identity Hub- When clicked on edit info from user menu action, user account edit page should get open instead of user display page

  20. CTRL+K: When any feature/module is already opened and user press ctrl +k button from keyboard then search filter modal is getting opened at back

  21. Delegation - Delegator and Delegatee consent should not get updated if user has already set some other consent

  22. Users> Group- Rename the label from 'Delete' to 'Unassign'.

  23. Audit- Logs for deprovisioned user is getting repeated.

  24. Custom Field- Policy Map- Date is not showing in correct format

  25. Mobile app- When clicked on user name for first time after killing app , keyboard is getting hidden

  26. Custom Attribute-Provision- When a custom attribute with special characters is created and applied in a provision rule (for user creation), the provision rule fails to trigger after the user is created.

  27. Global search (Ctrl+K) - even if characters are not matching still showing suggestions

  28. User setting- Error message should be shown when any action is performed and when landing/refreshing setting page

  29. Cymmetri Selfservice App - Need to change the message showing in popup screen while TOTP is getting authenticated.

  30. Mozilla Browser specific- User getting stuck when password less Webauthn is On

  31. Application - SSO - While clicking on Preview assertion , getting error "processing please wait"

  32. Product menu getting hide on workflow page: a. Menu action- Displaying an error message when a user already has one role assigned and tries to assign a menu action.

  33. User info page gets crashed while user edit fails

  34. Import/Export- Showing error message when importing file into new tenant (AD specific)

  35. Custom Attribute-Provision- When a custom attribute with special characters is created and applied in a provision rule (for user creation), the provision rule fails to trigger after the user is created.

  36. Quick setup- Data is not getting reset after closing policy mapping popup box, but getting reset when clicked on "I ll do later button"

  37. Add Page Number support for Amaya

  38. Application - SSO While saving the same config in two applications, while clicking on Edit SP config , popup showing do you want to continue editing the SP configuration? but only continue button is given

  39. Application - SSO - While saving the configuration in new application, save button loader is loading continuously

  40. 360 recon-Hide runnow button from detail view

  41. 360 recon dashboard filter-add dropdown for break type

  42. 360 recon dashboard-label change account overdue to account overdue in the target (also add some info on i icon what is this)

  43. 360 recon-Already running recon need to handle,disable play button or show message

  44. 360 dashboard-make label consistent

  45. 360 recon dashboard-action details showing blank

  46. 360 Degree recon-For execution showing error

  47. 360 Degree Recon- History some time loading some time not

  48. Recon 360 recon- Validation message for missing data is not required as it already shows no data found on page when recon is not executed at all

  49. 360 recon dashboard-action details showing blank

  50. 360 dashboard-Search not working on break type

  51. 360dashboard-loginid filter not working

  52. 360 recon detail data showing mismatch

  53. 360 recon execute audit log not present

  54. 360 recon dashboard-on 2nd run details getting repeated

  55. Amaya Azure- Showing route issue error message

  56. Import Application- UI for name is not proper

  57. Import/Export- Recon is not working for AD new application bundle

  58. Teams config - while removing the condition in Group condition, showing error " Please try again"

  59. On Behalf config - while removing the condition in Group condition, showing error " Please try again"

  60. Teams Config - If condition is kept blank and save is clicked , getting error " Please try again"

  61. On behalf config- If condition is kept blank and save is clicked , getting error " Please try again"

  62. Import/Export Application- Convertor field types in policy map is not getting imported

  63. Import/Export - When any application configuration is imported into a new tenant, the user should be redirected to the application provisioning page after the upload

  64. Import application- Showing an error message when importing an Amaya-based application if the exported application was without the policy map checked

  65. Amaya- Policy Map Password attribute datatype identified as password instead of string

  66. Amaya- Rename all operations(Test, Search, Sync, etc....) in sentence case

  67. Workflow- Even after updating Grade as the 2nd level approver in the workflow, the 1st level approver is still being set at level 2

  68. Workflow- After updating the user list as the 2nd level approver in the workflow, the 1st level approver is still being set at level 2

  69. Workflow- When the level 3 approver is updated in the workflow, a 'Workflow Not in Range' error message is displayed.

  70. Workflow- Even after updating the reporting manager as the 2nd level approver in the workflow, the 1st level approver is still being set at level 2

  71. Workflow- When workflow over workflow is applied 2nd level approver is not getting updated

  72. 360 recon should consider full sync

  73. 360 recon fails then that 360 recon should be abort

  74. Amaya Felicity Role assignment- Taking time to provide error message

  75. Deprovision- Exclusion Application- Application going in pending deletion state when that particular application is added in exclusion application while manually deleting user from Identity hub

  76. 360 Recon sync with bulk data showing heap size issue

  77. AD new application- User list is not getting displayed showing urersrvc unknown error.

  78. My workspace> Inbox- When workflow assignment is reassigned by admin, then previous approver should not be able to accept or reject request if page is already open in previous approver account.

  79. Inbox - Workflow Request for setup for application - Need to enhance the details as per user interface.

  80. Error in the server log-authsrvc ,No impact on functional flow

  81. After the campaign workflow triggered on revoked, even though the campaign had ended and the workflow was approved, applications were still getting unassigned.

  82. Campaign - Reviewer can approve self review request

  83. Campaign not getting end, for tenant 2711

  84. Workflow TAT- Workflow is getting aborted when grade is set at second level approver and set TAT time is over

  85. Workflow TAT- Workflow is getting aborted when 2 level approver is set and set TAT time is over

  86. Workflow TAT- Workflow is getting aborted when workflow approver is assigned to user list

  87. Workflow TAT- Showing error when user is not present and TAT is over

  88. Workflow TAT- Showing unauthorized error when TAT is over and operation is getting aborted

  89. Recon pull- with both exist link, audit detail not showing

  90. Workflow rule configuration-on edit workflow ,previously selected role getting save

  91. AD new bundle- Managed View- View should be proper while separating multiple OU in proxy addresses

  92. AD new bundle- Manager and account expiry is not visible in Managed view

  93. AD new bundle- managed view- Value is not displayed in proper format in Name in managed view

  94. AD new bundle- Managed View- Showing different Start time/created time

  95. In User creation workflow L1 - User List approved , L2 - reporting manager , after TAT is expired , request is not getting auto reject.

  96. Pending Workflow List - If approver is User list and Grade then it should display in Current Assign in pending list

  97. User Workflow - If reporting manager is set as 2 level approver , reporting manager is showing as Unknown

  98. Policy Map- When attribute is searched via search button and that attribute is deleted then other attributes are not getting loaded

  99. Profile Picture- After clicking once on the upload button, that button should be disabled

  100. PAM-Server access not getting terminated even after time end (Related to HA environment only)

  101. User - Assign Application - Workflow initiated - Workflow Approvals page displays User list in Grade type

  102. Pending Workflow -If L1 approver is User List , then while clicking on the info icon, popup not showing user list .Also it is " Grade List Details"

  103. PAM-Server access not getting terminated even after time end (Related to HA environment only)

  104. Workflow Rule - Workflow is initiated when group is set as approver , group is not visible on popup screen

  105. AD new bundle>Group- When the "Sam account name" update checkbox is unchecked and user attempt to update the description, the description does not get updated in AD

  106. deployment_analytics_1 Service CPU utilisation is 100%

  107. Import/ Export- When file is exported from different env (Dev) and imported to QA env, then credentials are also imported along

  108. Security Bug Fixes :- E2E request/response payload encryption for all APIs of authservice

  1. manager notification : receiving user name required manager name

  2. Unable to identify application properties data type where value is empty

  3. Amaya || Create user operation fails due to invalid password

  4. In forgot password/password breach condition-asking disabled MFA factor also

  5. Amaya-Autofill policy map, When value is not present to the user at the time of application then amaya passing "$." to the target

  6. Campaign - Reviewer can approve self review request

  7. After the campaign workflow triggered on revoked, even though the campaign had ended and the workflow was approved, applications were still getting unassigned.

  8. Remote Group- AD Application- When users are removed from a remote group in Cymmetri, those members should also be removed from the group in Active Directory

  9. Amaya- Client id should be visible in encrypted form

  10. Provision Rule - While creating and configuring the custom attribute as "New ", system is not initiating the rule.

  11. AD new bundle- When an AD application is assigned to a remote group, the application is highlighted in the background while assigning but disappears as soon as the application popup box is closed

  12. Reports- When report is scheduled, Scheduler history is showing content not found and execution status is getting aborted

  13. AD Application- When Ad test provision is failed, and user trying to delete application from user account, then application should go in fail deletion state

  14. Audit- Taking time to load audit logs

  15. AD Application- Showing error when inserting start date in AD

  16. In application setting if show to user flag off then also application show in recent application.

  17. User lock- When a user account is active, and the same account is logged in through another browser and by any means account gets locked, the first session should get terminated.

  18. Branding- When show Unlock link from branding is kept as No, and admin user account gets locked, then user is not able to unlock account from login page

  19. Application- When user is adding /removing role then it is not getting reflected without refreshing

  20. group push-not taking user in AD at the time of update

  21. Passwordless- WebAuthn; Showing not allowed error

  22. Delegation-On behalf: when login by delegate and on-behalf condition is not satisfied still showing on-behalf toggle button and getting removed when refreshed

  23. AD Application- Group name should not accept space while creating or updating group name

  24. Audit- Audi log should show log when user is not getting any records in Recon history but showing task executed

VERSION
New Feature
Fixes
Known Bugs

3.1.3 Beta (26 July 2024)

  1. User Threshold: a. A UI change has been made in the general configuration for the threshold. b. Creation of user c. Updation of user d. Deletion of user e. Staging for user threshold f. Retry staging user from staging dashboard. g. Archive for user threshold h. Notification for user threshold

  2. User directory search API updated for quick search (keyword): a. Support dropped for: grade, userType, department, designation, custom-attributes b. Supported on: employeeId, email, mobile, firstName, lastName, middleName, displayName, login

  3. Data logger service version info added.

  4. Tenant registration database creation process optimisation.

  5. Pending Workflow Inner page applied functionality to reassign user from inner page

  6. Added QR code zoom feature on FIDO, TOTP and push Authenticator scanner.

  7. VPT: Modify routes of api - /usersrvc/api/user/directory/list/{appId} remove user role form routes.

  8. Custom Attribute support in following Workflow Rule Events a. User Creation b. Application Provisioning c. Application Deprovisioning d. Application Update

  9. Added the following templates in Amaya Quick Setup: • Atlassian • Zoho CRM • Zoho Desk • Zoho Books • Zoho Expenses

  10. Provided support for integer values for ROLE assignment through Amaya.

  11. Tenant Registration Process Resumption: In the event that the tenant registration process is interrupted, it can be seamlessly resumed and completed using the existing account configuration. The registration process can be resumed from the following stages: a. Pending OTP Verification b. Incomplete Credential Setup

  12. Active Directory || SimpleAD Connector upgrade: a. UserAccountControl attribute support added b. memberOf attribute support in manage system viewer c. ProxyAttribute attribute support added

  13. External IDP SSO: a. added support to login into cymmetri as external identity provider as idp initiated sso.

  14. SAML IDP SSO: a. added support to send idp initiated (cymmetri) sso response to cymmetri as service provider.

  15. TOTP Config

  16. Removal of Email validation from backend

  17. DataLogger | Refer configuration steps here: a. data-logging framework optimisation. b. Full sync support, this step is optional step and required only if, • Tenant audit database is not present, or • Tenant audit database is corrupt so fresh setup is required.

  1. Error in the server log-authsrvc ,No impact on functional flow

  2. Team config - Create - Discard button issue - After clicking not able to add the details in condition section

  3. Rule engine- Remove "above" word from note

  4. login with admin-Campaign detail show role also, currently role showing only for campaign manager

  5. Amaya API returning null if error instead of error and errorCode

  6. Hide metabase analytics

  7. Workflow rule configuration-on edit workflow ,previously selected role getting save

  8. User - Assign Application - Workflow initiated - Workflow Approvals page displays User list in Grade type

  9. Pending Workflow -If L1 approver is User List , then while clicking on the info icon, popup not showing user list .Also it is " Grade List Details"

  10. Identity Hub- Pending initial login symbol is visible far away from user name

  11. On behalf configuration - While disable and enabling the toggle,popup message shows "This change will take effect on user's next login" but it is getting reflecting on the fly.

  12. On-behalf>Delegation- On behalf menu is not visible when logged in via Delegatee account

  13. SSO- Group mapping- Save button should be enabled when mandatory fields are filled

  14. Workflow- Even after updating the reporting manager as the 2nd level approver in the workflow, the 1st level approver is still being set at level 2

  15. Global search (Ctrl+K) - even if characters are not matching still showing suggestions

  16. Product menu getting hide on workflow page

  17. LDAP connector-LDAP SSL should be save in Boolean in the DB

  18. User setting- Error message should be shown when any action is performed and when landing/refreshing setting page

  19. User setting- External idp rule is active-An admin user should not be able to lock a user when the external IDP rule matches the user condition

  20. Schedule history-ad by default todays filter for from and to

  21. Teams config- When the view button is clicked, the user is still able to check or uncheck the boxes

  22. Menu action- Displaying an error message when a user already has one role assigned and tries to assign a menu action.

  23. Custom Attribute-Provision- When a custom attribute with special characters is created and applied in a provision rule (for user creation), the provision rule fails to trigger after the user is created.

  24. Lifecycle Management - All menus - Discard button is not working as expected.

  25. Application - SSO While saving the same config in two applications, while clicking on Edit SP config , popup showing do you want to continue editing the SP configuration? but only continue button is given

  26. Application - SSO - While saving the configuration in new application, save button loader is loading continuously

  27. Amaya- Rename all operations(Test, Search, Sync, etc....) in sentence case

  28. Group Policy map- For group custom attribute Cymmetri field type should be automatically selected as working in users custom field

  29. Teams config - while removing the condition in Group condition, showing error " Please try again"

  30. On Behalf config - while removing the condition in Group condition, showing error " Please try again"

  31. Teams Config - If condition is kept blank and save is clicked , getting error " Please try again"

  32. On behalf config- If condition is kept blank and save is clicked , getting error " Please try again"

  33. Import/Export- Showing error message when importing file into new tenant (AD specific)

  34. Import application-show error message user or groupwise

  35. Import application- Showing an error message when importing an Amaya-based application if the exported application was without the policy map checked

  36. Import/Export - When any application configuration is imported into a new tenant, the user should be redirected to the application provisioning page after the upload

  37. Amaya Azure- Showing route issue error message

  38. Import/Export Application- Convertor field types in policy map is not getting imported

  39. Import/Export- Recon is not working for AD new application bundle

  40. Workflow- When workflow over workflow is applied 2nd level approver is not getting updated

  41. Workflow- Even after updating Grade as the 2nd level approver in the workflow, the 1st level approver is still being set at level 2

  42. Workflow- After updating the user list as the 2nd level approver in the workflow, the 1st level approver is still being set at level 2

  43. Workflow- When the level 3 approver is updated in the workflow, a 'Workflow Not in Range' error message is displayed.

  44. Workflow TAT- Workflow is getting aborted when workflow approver is assigned to user list

  45. Team config - Create - Discard button issue - After clicking not able to add the details in condition section

  46. Import/Export- By default, the time in the application name should be removed when exported

  47. Rule engine- Remove "above" word from note

  48. login with admin-Campaign detail show role also, currently role showing only for campaign manager

  49. Hide metabase analytics

  50. Error in the server log-authsrvc ,No impact on functional flow

  51. AD new application- User list is not getting displayed showing urersrvc unknown error.

  52. Campaign not getting end, for tenant 2711

  53. Workflow rule configuration-on edit workflow ,previously selected role getting save

  54. AD application new bundle - When SAMaccount name is set to false in Group policy map, members are not assigned in group when recon Pull is executed for both exist=Update

  55. My workspace> Inbox- When workflow assignment is reassigned by admin, then previous approver should not be able to accept or reject request if page is already open in previous approver account.

  56. After the campaign workflow triggered on revoked, even though the campaign had ended and the workflow was approved, applications were still getting unassigned.

  57. Workflow TAT- Workflow is getting aborted when grade is set at second level approver and set TAT time is over

  58. Workflow TAT- Workflow is getting aborted when 2 level approver is set and set TAT time is over

  59. Workflow TAT- Showing error when user is not present and TAT is over

  60. Workflow TAT- Showing unauthorized error when TAT is over and operation is getting aborted

  61. User - Assign Application - Workflow initiated - Workflow Approvals page displays User list in Grade type

  62. Reports- SSO based application- Reports are blank/ not showing data when SSO based application are accessed

  63. Pending Workflow -If L1 approver is User List , then while clicking on the info icon, popup not showing user list .Also it is " Grade List Details"

  64. AD new bundle>Group- When the "Sam account name" update checkbox is unchecked and user attempt to update the description, the description does not get updated in AD

  65. Import/ Export- When file is exported from different env (Dev) and imported to QA env, then credentials are also imported along

  66. Identity Hub- Pending initial login symbol is visible far away from user name

  67. On behalf configuration - While disable and enabling the toggle,popup message shows "This change will take effect on user's next login" but it is getting reflecting on the fly.

  68. In User creation workflow L1 - User List approved , L2 - reporting manager , after TAT is expired , request is not getting auto reject.

  69. On-behalf>Delegation- On behalf menu is not visible when logged in via Delegatee account

  70. Import Manager-Manager is deleted and user trying to assign then in the import history showing success but in audit showing failed

  71. Application delete-Campaign-Deleted application available for review

  72. AD new bundle- User policy map- When Sam account name is mapped with any attribute and update checkbox is kept false, and user is updated, audit log is showing failed

  73. Workflow>Inbox- Address fields name in inbox /pending workflow and identity hub users are not same

  74. SSO- Group mapping- Save button should be enabled when mandatory fields are filled

  75. Campaign-email report showing error

  76. deployment_analytics_1 Service CPU utilization is 100%

  77. Application - Form - When submitted as blank, after assigning the application page is getting blank.

  78. Reports- Records are getting displayed after 11min approximately

  79. Csv Import users- An error message is not shown when the user is unable to save user details if a space is included in the email

  80. After the campaign workflow triggered on revoked, even though the campaign had ended and the workflow was approved, applications were still getting unassigned.

  81. User Workflow - If reporting manager is set as 2 level approver , reporting manager is showing as Unknown

  82. Workflow>Inbox- Address fields name in inbox /pending workflow and identity hub users are not same

  83. Export- Rename Config type to Select All

  84. MFA- When default MFA rule is inactive, user is able to delete default rule as well

  85. Amaya connector>Policy mapping- Bottom slider should be fixed

  86. Amaya || Validation preventing usage of long valid header

  87. Amaya Connector- By default only green colored (confirmed policy attributes) only should be checked

  88. Amaya Quick Setup- When an auto test run fails and operations are manually updated, clicking 'Generate Policy Mapping' should exit the page.

  89. Application delete-Campaign-Deleted application available for review

  90. Import Manager-Manager is deleted and user trying to assign then in the import history showing success but in audit showing failed

  91. Import/Export- By default, the time in the application name should be removed when exported

  92. SSO - OpenID - Configure CIDR - Add - While clicking on Add icon without entering any details , blank data is getting added.

  93. SSO - OpenID - Configure CIDR - While clicking on delete icon ,no message is getting displayed and entry is getting removed

  94. Workflow List - View - Showing label as "Custom Workflow "

  95. Import/ Export- Application name while importing file should be limited to 50character

  96. Application - SSO - SLO toggle enable/disable audit log

  97. SOD; policies-Policy owner name is not getting updated after updating user name from Identity hub and without owner name policy is getting saved

  98. AD new bundle- When recon is executed for both exist update but application is not linked, still user is getting updated.

  99. Application - Form - When submitted as blank, after assigning the application page is getting blank.

  100. Masters - Grade- While clicking on Add button it is showing edit page of existing record

  101. Tenant registration- Showing suspicious popup box when clicked on verify your email

  102. New tenant registration- If tenant is already on registration page then after clicking verify email from mail box should show tenant is already registered

  103. Tenant registration- Taking time to register tenant

  104. Email verification - Email verify link is redirecting to otp verification screen.

  105. My Workflow> Teams- Add short menu button

  106. Tenant creation not working

  107. After release v 3.1.2, for old updated tenant campaign module is disabled

  108. Portal-For module update showing error, already exist

  109. Push and FIDO scan zoom functionality not available at the time of Device MFA

  110. Push and FIDO scan zoom functionality not available at the time of application MFA

  111. User setting- External idp rule is active-An admin user should not be able to reset user password when the external IDP rule matches the user condition

  1. manager notification : receiving user name required manager name

  2. In application setting if show to user flag off then also application show in recent application.

  3. Unable to identify application properties data type where value is empty

  4. Amaya || Create user operation fails due to invalid password

  5. User-Email with invalid email id like NA, this user not able to use MFA with OTP

VERSION
New Feature
Fixes
Known Bugs

3.1.4 Beta (13 August 2024)

  1. UI/UX || Warning added || Application Config Import Modal || Auto 'Create Only' for User Principal policy mappings

  2. A new feature has been developed for the "Recommendation Engine", enabling seamless integration and management of application and role recommendations. The recommendation engine supports the generation of personalised application and role suggestions for each user. The system supports the automatic synchronisation of data from various sources, ensuring that recommendations are always based on the user behaviour. All recommendation engine configurations, data synchronisation are stored and can be easily retrieved and updated as needed.

  3. UI/UX || Amaya || Add support for JSON body validation through validate button

  4. Audit log comparison for oldObject and newObject when they are in detailed format

  5. UI/UX Inconsistent buttons placement in some module fixed to a default below position

  6. UI/UX Onboarding walkthrough of New users

  7. ICICI: a. The inbox title in the workflow setup event has been updated to display the workflow name. b. Workflow (Pending workflow list) requester and requestedFor column added for display

  8. Identity Analytics (Reporting Engine)

  9. End to End Request/Response Payload Encryption for all authservice's API. (/authsrvc/*)

  10. User Threshold (Phase 2): i. Update Email Title and Template ii. Create a new 'Move to Archive' button to manually archive a user. iii. Make the notifications field mandatory in the User Threshold Configuration. iv. Added the Org Admin as the default notifier in the user threshold configuration.(Not supported for old tenant). v. Update UI Error Message Format vi. The User Threshold staging mode name has been changed. vii. Failure to Move Staging User to Archive Manually and Audit Log Display for fail. viii. The changes made to the staging dashboard view. Include a comparison between the previous and updated versions of the UI. ix. Show the display name in the Threshold Delete operation on the Staging Dashboard. x. Notification Field in User Threshold Config for delete users.

  1. Amaya- When server connector timeout is changed and test configuration is clicked, it is showing "connector not found in cloud" error in Audit log

  2. Import User - If loginid already exist , then remark shows "Usrsrvc.existing Login" . Change this text to "Existing Login Id"

  3. Import/Export- Showing host server details when file is imported for script connector

  4. My Access - Tags - Roles is not getting displayed in Application

  5. Application - Clicking on the role tile ,SSO is happening and also while clicking on close icon, SSO is happening

  6. Applications- When any attribute is updated (made empty in the target application) and recon for both exist operation is executed, the corresponding attribute in Cymmetri should also be cleared

  7. Reports- SSO based application- Reports are blank/ not showing data when SSO based application are accessed (To correct the data need to perform data-logger sync for respective tenant. Refer configuration steps here)

  8. Deprovision- User is getting deprovisioned even after user status is changed to Active from Inactive

  9. User threshold mail notification- Title changes required

  10. Audit log-Recon - When recon is executed with status as Inactive, audit log is showing "Recon initiated successfully" but not any log for execution failed/aborted

  11. Audit Filter- Add cross button in Target Type and Action field.

  12. Threshold Config- Validation message for all three operations should be similar

  13. Threshold Create/Update- Spelling for exceeded is not correct

  14. Notification Template - Toggle and status should display in status column as per other modules.

  15. Create User- While creating user on newly created tenant, assign group page showing text "No group assigned , assign group"

  16. User setting- External idp rule is active-An admin user should not be able to reset user password when the external IDP rule matches the user condition

  17. Create user - While creating user on newly created tenant, assign application page showing text "No data found, add application"

  18. Audit Filter- Add cross button in Target Type and Action field.

  19. Portal-For module update showing error, already exist

  20. My Access - Tags - Roles is not getting displayed in Application

  21. Threshold Config- Validation message for all three operations should be similar

  22. Threshold Create/Update- Spelling for exceeded is not correct

  23. Notification Template - Toggle and status should display in status column as per other modules.

  24. Create User- While creating user on newly created tenant, assign group page showing text "No group assigned , assign group"

  25. Create user - While creating user on newly created tenant, assign application page showing text "No data found, add application"

  26. Group Unassignment: The message appearing on group unassignment is incorrect

  27. Push and FIDO scan zoom functionality not available at the time of Device MFA

  28. Push and FIDO scan zoom functionality not available at the time of application MFA

  29. Campaign Reassign -inactive users are also listed for reassignment on click

  30. Login page- AD auth- Provide proper UI message when AD adapter details are incorrect

  31. Amaya- When server connector timeout is changed and test configuration is clicked, it is showing "connector not found in cloud" error in Audit log

  32. Import User - If loginid already exist , then remark shows "Usrsrvc.existing Login" . Change this text to "Existing Login Id"

  33. User threshold- Pending Staging- When changing page select all box should be unchecked.

  34. Threshold Pending staging- Whenever the page changes or the number of records per page is modified, the selection should be reset

  35. Import/Export- Showing host server details when file is imported for script connector

  36. Threshold pending staging- When the retry button is clicked multiple times, the validation message does not appear after the third click on UI

  37. Application assignment- Change user search suggestion watermark

  38. Onboarding registration- When resolution is at 80%, PAM report admin option is not visible in dropdown

  39. Reports- SSO based application- Reports are blank/ not showing data when SSO based application are accessed

  40. After release v 3.1.2, for old updated tenant campaign module is disabled

  41. Onboarding registration- When an application is selected and then reverted to the previous page, selecting the application again causes the application count to double

  42. External JIT- JIT configuration should be disabled until new external idp configuration details are filled

  43. External IDP- JIT- API is showing "undefined" error on clicking JIT button and on enabling JIT configuration

  44. External IDP- JIT- Reverse the title, it is confusing for user

  45. MFA - Secret Question - Question selection is getting non-selectable after entering incorrect answers and then retrying for correct answer

  46. My workspace>Inbox- Count is not showing when records are in claim

  47. Reports( Employee's with upcoming contract end date) - By default date filter should be applied of 30 days

  48. Provision Rule - Cursor of the condition is getting overlapped with footer of the page.

  49. Onboarding - Login credentials timeout error

  50. My Access - Superset Application logo and label should be changed

  51. Applications- When any attribute is updated (made empty in the target application) and recon for both exist operation is executed, the corresponding attribute in Cymmetri should also be cleared

  52. Deprovision- User is getting deprovisioned even after user status is changed to Active from Inactive

  53. Audit log-Recon - When recon is executed with status as Inactive, audit log is showing "Recon initiated successfully" but not any log for execution failed/aborted

  54. User threshold mail notification- Title changes required

  55. Application- Managed view- When manager is removed from Cymmetri, user is still getting displayed in managed view

  56. Create Threshold Config> Csv import- Showing empty records in pending staging list when threshold limit is exceed and user are imported via csv file

  57. Reports- SSO based application- Reports are blank/ not showing data when SSO based application are accessed

  58. My workspace>Inbox- Count is not showing when records are in claim

  59. login with admin-Campaign detail show role also, currently role showing only for campaign manager

  60. Cymmetri Selfservice App - Once we click on the web link from scanner , it should show confirmation popup on screen (Suggestion)

  61. Selfservice Mobile App - When app is in Quit state and open the app via scanner(camera), it is not redirecting to login page of the website

  62. Push Authenticator - Need to change the error message

  63. User creation- While creating new users then going to next level that is on groups page and then on application page ,then user should be redirected back to the group's page when back button is clicked instead of existing user creation page

  64. Showing error when saving workflow with name( User creation, Application provisioning, Application deprovisioning)

  65. deployment_analytics_1 Service CPU utilisation is 100%

  66. Campaign-email report showing error

  67. Some time tenant registration not working,showing WriteConflict error in the service

  68. Application provisioning and deprovisioning workflow initiated request is not getting displayed in activity logs.

  69. Workflow Rules - Application Deprovisioning event - If condition is set as RegEx for custom attribute is not working

  70. User update-Showing audit failed-Write conflict

  71. Report - Updated record should display on top.

  72. Auth rule showing unknown error

  73. Workflow List - View any workflow detail - While clicking on info icon it is showing Grade List Detail

  74. AD-Recon-If Policy attribute marked inactive then also it is getting pull from AD

  75. Login via Application admin- When click on application showing processing please wait error message

  76. Applications- Application are not getting assigned to user and also audit log is not visible for the same

  77. PAM write admin not able to assign users, user list not populating

  1. manager notification : receiving user name required manager name

  2. In application setting if show to user flag off then also application show in recent application.

  3. Unable to identify application properties data type where value is empty

  4. Amaya || Create user operation fails due to invalid password

  5. Reports- Records are getting displayed after 11min approximately

VERSION
New Feature
Fixes
Known Bugs

3.1.5 Beta (6 August 2024)

  1. UI/UX - Workflow Inbox User detail will now have applications detail as well assigned to the user

  2. UI/UX - Workflow Inbox will have start date and end date filter

  3. User delete workflow support a. Workflow configuration support b. Rule configuration support

  4. CISO Dashboard - REVERTED

  5. Amaya || General Config based role data type

  1. PAM write admin not able to assign users, user list not populating

  2. Policy map- Empty value are getting saved in policy mapping

  3. Workflow Rule update - View - Created by and updated by fields are empty

  4. Superset - OpenId issue - While doing sso for superset application, it should is getting redirect superset url with error "The request to sign in was denied"

  5. Threshold configuration- Replace could be to can be

  6. Policy Map- When searching in the search box by any attribute, the search should get reset after changing tabs

  7. Onboarding - Login credentials timeout error

  8. Application- When searching user in application, user can be searched by first name, last name, login id but not by First name+lastname

  9. PAM write admin not able to assign users, user list not populating

  10. TOTP-Lookahead window change , on click save button show warning message,

  11. User delete Workflow - Pending Workflow - Application details tab is not present

  1. manager notification : receiving user name required manager name

  2. In application setting if show to user flag off then also application show in recent application.

  3. Unable to identify application properties data type where value is empty

  4. Amaya || Create user operation fails due to invalid password

  5. Reports- Records are getting displayed after 11min approximately

  6. Deprovision Rule executed via Scheduler - Workflow is not getting initiated for the set of users on the basis of status/end date

  7. Workflow List - Getting error " Contact system administrator" on technova tenant

Version
New Features
Fixes
Known Bugs

3.1.6 (10 September 2024)

  1. Form Logic - The FormLogic functionality, enables you to store custom data using flexible, administrator-defined forms. It empowers you to create forms tailored to your specific data collection requirements, providing a versatile solution for various data management needs. 360 Degree Reconciliation - Compare tab added to the current feature, where user can compare with the source application and target application and further generate reports and download csv.

  2. SkipPasswordExpiry - We are enhancing our Password Policy by introducing a new field

  3. SkipPasswordExpiry, within the PasswordChangeRule. This enhancement allows users to opt out of the password expiry process entirely. When the SkipPasswordExpiry field is enabled, users will not receive warnings or notifications about password expiry, nor will they be prompted to change their password due to its expiration.

  4. Connector: SimpleLDAP application.

  5. ICICI Client - Role Based form delivery in IGA.

  6. SDK based integration to send mobile push notifications to mitigate legacy API issues: a. Fido Based Notifications b. Normal Push Based Notifications The LDAP adapter has been updated with a new feature that eliminates the need to enter a username and password for each execution.

  1. Form logic-Configured Forms -On click setting icon screen getting flicker

  2. Selfservice Submit form-Update error message and backend error code if pre and post hook script h

  3. Form logic-on form submit close form

  4. Form logic-Selfservice-My Form Submissions pagination, page getting blank

  5. Archived Forms detail-Revision data showing wrong, showing non existing list

  6. Form logic-After changing form schema, form detail showing blank

  7. Form logic-User submissions-Provide search by taskeid, username, loginid

  8. Form logic-on all screen search only working for the exact case, expected should be work for matchin

  9. Form logic-Form table-sorting not working

  10. Form logic-Pre and post hook should be non mandatory

  11. Form map with rule-if form map more than defined limit then error message showing only one time

  12. Staging users details - Version history log user details not loading

  13. Form logic-Configured form and archive form detail, back button behaviour is not as expected, need

  14. Form logic-Form Access Rules-Link form, save button should be disabled till form selection

  15. form logic- if request is timeout or fail then feature showing disabled

  16. Form logic-User submissions-Provide date filter

  17. Workflow || Additional Form Info || Readonly text-based form submissions

  18. Timebased Application: Timebased application assignment message spelling incorrect

  19. Deprovision- When applications are assigned via group and deprovision is executed all the application

  20. Teams - Suspended Users - List View - Edit - It is redirecting to Users but showing a blank screen

  21. Application Search: When clicking on "View More Applications" and searching for an application, the

  22. Pending Staging- When no records are present on the page, the "Select All" button should be disabled

  23. User Onboarding - Dropdowns are not loading when creating a user after adding an Admin during t

  24. Global search - Pending action is not coming in global search

  1. manager notification : receiving user name required manager name

  2. In application setting if show to user flag off then also application show in recent application.

  3. Unable to identify application properties data type where value is empty

  4. Amaya || Create user operation fails due to invalid password

  5. Reports- Records are getting displayed after 11min approximately

  6. Deprovision Rule executed via Scheduler - Workflow is not getting initiated for the set of users on th

  7. Workflow List - Getting error " Contact system administrator" on technova tenant

  8. FormLogic || Step 2 of form || Form config JSON should be mandatory

Admin Dashboard

Cymmetri dashboard provides administrators with a centralized and visual representation of key information and controls related to identity management, access governance, and administration.

The dashboard serves as a command center for overseeing and managing the identity lifecycle, compliance, and other aspects of identity and access governance within an organization.

Upon Logging in the admin is landed on the dashboard where they can see the following:

  • Shortcut to configure recently added application - Configuration means adding roles, defining provisioning, reconciliation, SSO, etc.

  • Users Activity - Total Successful user logins in Cymmetri on that day

  • Accounts Locked - User account locked event on that day

  • Users Onboarded - New users being onboarded in the system on that day

  • Password reset - Password reset activity in the system on that day

  • Authentication stats - Number of successful and failed login attempts in a timeframe

  • App Identity - It displays the application reconciliation activity with respect to the users.

Cymmetri also displays some important system KPIs to the admin as shown below

Application - Number of applications onboarded in Cymmetri

Active Users - Total number of active users in the system

Total Users - Total number of users onboarded in Cymmetri

Roles - Total application roles created in Cymmetri

Workflows - Total approval workflows created in Cymmetri

Password policy - Total number of password policies created for user authentication in Cymmetri

Rules - Total rules created in the System for provisioning, MFA, approval workflows, etc.

Users unlogged - Number of users who have never logged in to Cymmetri

Additionally, there are some useful system shortcuts placed on the right side of the page to make faster business decisions.

Starting your Cymmetri Trial

  1. Enter your country, and phone number (mandatory to receive OTP), and enter a domain name for your tenant. In case the domain available message is not shown, choose a different domain name. Click on the Start Trial button.

  1. You will receive an OTP on your mobile number from the previous step. Enter the OTP here and wait for a few seconds for your tenant to be created.

  1. You will be redirected to your domain to create the first Organization Admin user. Ensure that your password matches the password policy.

  1. You will receive a message to show that your tenant has been created.

  1. Click on the Login button to proceed with the onboarding process

  2. Enter your username and press Next

  1. Enter your password and proceed with the setup of your tenant by clicking on the Login button.

  1. Choose applications from the application catalogue, and click on the application icon for all the applications you wish to add. Then click on the Next button.

  1. Enter details to create a second administrator account. Click on the Send Invite button to create an administrator. Click on the Next button to proceed.

  1. (Optional) Add users if you wish to. Then click on Finish.

  1. You will be redirected to the Dashboard to proceed with the system.

Next Steps:

  1. Manage your users and groups.

Accessing Cymmetri

To access Cymmetri, users must use a web browser, such as Google Chrome or Safari, and enter the appropriate address in the address bar as shown below:

URL: https://<companyname>.cymmetri.com/login

Example: https://helpdocs.cymmetri.com/login

Once the address is entered it opens a page as shown below, where the users may enter their username and password to access Cymmetri.

General Config

In this section within Cymmetri, a range of general or broad configuration settings and options are managed. These settings encompass various foundational configurations that affect the overall behavior of Cymmetri.

There are different system configurations in Cymmetri mentioned below:

On Behalf

Time Based

In the Time-Based configuration, system administrators can determine whether the system will send repeated notifications to users based on the number of days remaining, as specified in the 'Send Notifications before' field. This occurs when an application is assigned to the user as a time-based application and is about to expire.

Email Config

These settings and configurations within Cymmetri are specifically related to the management and customization of email-related functionalities. This configuration area allows administrators to set up, manage, and customize, the email communications as per the organization's needs.

Suspend Config

Within the Suspend Config section, administrators have the ability to determine the duration a user remains in a suspended state before transitioning to the archived users' section. This can be specified using the "Suspend After" setting.

Scheduler Integration:

The system incorporates a scheduler feature, enabling administrators to automate the transition of users from the suspended state to the archived state. The scheduler runs within defined time frames, streamlining the management of user statuses.

As an example, if the "Suspend After" configuration is set to 0 days, a user will promptly move to the archived users section upon suspension. This allows for flexibility in tailoring user management to specific organizational needs.

Workflow Preference Config

Within the Workflow Preference Config, administrators have the ability to specify the visibility and editability of workflows associated with user access requests for a particular application. This setting allows for tailored control over how approvers interact with the configured workflow.

Visible to the User:

When this option is selected, approvers for the requested application are visible to the user initiating the access request. Transparency is maintained throughout the workflow process.

Hidden from the User:

Opting for this configuration ensures that approvers for the requested application remain hidden from the user. The workflow operates discreetly in the background without user visibility.

Editable by the User:

If this preference is chosen, users initiating access requests have the ability to select approvers based on their availability, providing a more dynamic and user-centric workflow experience.

This functionality applies if a workflow has been configured for the specified application, offering flexibility in managing user access requests in alignment with organizational requirements.

The approvers mapped in the workflow can only be edited only if they are part of the "user list" in workflow configurations.

In conclusion, if the workflow preference config is set to Editable, the requester will only be able to select the approver from the workflow if the approvers are part of a user list.

Reset Password OTP Config

This setting involves whether an OTP (One-Time Password) is required as an additional verification step when users attempt to change their passwords.

User Decommission Config

The User Decommission Config is a vital feature in Cymmetri, allowing administrators to automate user decommissioning based on login activity.

In this configuration, actions are triggered if the user hasn't logged in to Cymmetri in N number of days

Config Days: Set the threshold for user inactivity in terms of days. Users who have not logged in for the specified duration will be subject to the defined actions.

Actions: Choose from three distinct actions to be taken when the specified inactivity threshold is reached:

  • None: No action will be taken based on user inactivity.

  • Inactive: Users exceeding the configured inactivity period will be marked as inactive.

  • Delete: Users who have not logged in for the specified duration will be suspended from the system.

Syslog Configuration

Syslog configuration in Cymmetri allows for the seamless integration of logging and event information with external Syslog servers. By defining specific parameters, administrators can ensure that critical system events, user access information, and other relevant data are transmitted in real-time to a Syslog server.

Syslog Config fields:

  1. Syslog Name - Assign a unique name to this Syslog configuration

  2. App Name - Specify the application name associated with this Syslog configuration.

  3. Server Host Name - Enter the hostname or IP address of the Syslog server that will receive log messages

  4. Server port - Define the port number on the Syslog server where log messages will be sent.

  5. Protocol - Choose the preferred protocol for Syslog communication - TCP or UDP.

In configuring these parameters, administrators tailor Cymmetri's interaction with external Syslog servers, optimizing the logging process to meet organizational needs.

Webhooks Configuration

Webhooks in the Cymmetri's admin module provide a powerful mechanism for real-time communication and integration with external applications or services. Administrators can configure various webhook settings to enhance the system's functionality and streamline interactions with external components.

Webhook Configs:

  1. Protocol - Communication protocol - (Static field)

  2. Method - HTTP method for webhook requests - (Static Set to post)

  3. Server - Enter the server or endpoint URL where the webhook payloads will be delivered.

  4. Server Context path - provide the context path for the specific service within the server.

  5. Secret - This secret key, known to both Cymmetri and the external service, helps authenticate the webhook requests.

  6. Token Expiry Minutes - Define the duration (in minutes) for which authentication tokens associated with webhook requests are valid.

Application Request Config

This setting determines if a user has the ability to initiate requests for new applications through the Cymmetri self-service page.

When the status is active, the user will see the "Add New" button on the "My Access" page within the "My Workspace" section. By clicking this button, the user can submit an access request for additional applications.

Threshold Delete Config

The Threshold Delete Config is a critical component in Cymmetri, governing the maximum number of users that can be deleted from the system in a single day.

This configuration provides an additional layer of control to prevent unintended mass deletions and ensure the security and stability of Cymmetri

Supported Web Browsers

Cymmetri supports the following web browsers:

Version of specific browsers supported by Cymmetri are:

DESKTOP:

MOBILE:

Help

The Cymmetri Help Page serves as a vital resource, offering users a comprehensive documentation hub that breaks down all the features and provides step-by-step configurations for various functionalities.

Key Features of the Help Page:

  1. Comprehensive Feature Explanation: The Cymmetri Help Page covers all the features of the platform straightforwardly. Whether you are a beginner or an experienced user, you can find detailed explanations of each feature, ensuring you have a clear understanding of its purpose and functionality.

  2. Step-by-Step Configurations: One of the highlights of the Help Page is its provision of step-by-step configurations for various features. This means you can follow a simple, structured guide to set up and customize different aspects of Cymmetri according to your specific needs.

  3. User-Friendly Language: The documentation is crafted in a manner that balances technical precision with user-friendly language. You won't find unnecessary jargon, making it accessible for users with varying levels of technical expertise.

Start by clicking on the link to start the registration of your tenant on the Cymmetri Cloud 2.0 and enter your personal details with your work email. Click on Next.

It refers to a setting within Cymmetri that enables a user to raise an application access request on behalf of another user. An administrator can enable this feature and then the user can raise a request for any other user. The page shows how the users get access to the On Behalf feature and use it to raise application requests

OS
Chrome
Firefox
IE
Edge
Safari
Browser
Version
Browser
Version

To access this valuable documentation, you can visit directly. Alternatively, you can simply click on the help icon located at the bottom left of your Cymmetri tenant screens.

register.cymmetri.io
Learn how new users can access your tenant.
Manage your applications.
Check out your workspace.
Add your own branding.

Chrome

66

Edge

16

Firefox

57

Opera

57

Safari

53

Chrome Android

12.1

Firefox Android

66

Opera Android

57

Safari iOS

47

Samsung Browser

12.2

3.1.3-Beta

(26 July 2024)

New Features

  1. User Threshold: a. A UI change has been made in the general configuration for the threshold. b. Creation of user c. Updation of user d. Deletion of user e. Staging for user threshold f. Retry staging user from staging dashboard. g. Archive for user threshold h. Notification for user threshold

  2. User directory search API updated for quick search (keyword): a. Support dropped for grade, userType, department, designation, and custom-attributes b. Supported on: employeeId, email, mobile, firstName, lastName, middleName, displayName, login

  3. Data logger service version info added.

  4. Tenant registration database creation process optimization.

  5. Pending Workflow Inner page applied functionality to reassign users from the inner page

  6. Added QR code zoom feature on FIDO, TOTP and push Authenticator scanner.

  7. VPT: Modify routes of API - /usersrvc/api/user/directory/list/{appId} remove user role form routes.

  8. Custom Attribute support in the following Workflow Rule Events a. User Creation b. Application Provisioning c. Application Deprovisioning d. Application Update

  9. Added the following templates in Amaya Quick Setup: • Atlassian • Zoho CRM • Zoho Desk • Zoho Books • Zoho Expenses

  10. Provided support for integer values for ROLE assignment through Amaya.

  11. Tenant Registration Process Resumption: If the tenant registration process is interrupted, it can be seamlessly resumed and completed using the existing account configuration. The registration process can be resumed from the following stages: a. Pending OTP Verification b. Incomplete Credential Setup

  12. Active Directory || SimpleAD Connector upgrade: a. UserAccountControl attribute support added b. memberOf attribute support in manage system viewer c. ProxyAttribute attribute support added

  13. External IDP SSO: a. added support to login into cymmetri as an external identity provider as IDP initiated sso.

  14. SAML IDP SSO: a. added support to send IDP initiated (cymmetri) sso response to cymmetri as a service provider.

  15. TOTP Config

  16. Removal of Email validation from the backend

  17. DataLogger | Refer to configuration steps here: a. data-logging framework optimization. b. Full sync support, this step is optional and required only if, • Tenant audit database is not present, or • Tenant audit database is corrupt so fresh setup is required.

Fixes

  1. Error in the server log-authsrvc, No impact on the functional flow

  2. Team config - Create - Discard button issue - After clicking not able to add the details in the condition section

  3. Rule engine- Remove the "above" word from the note

  4. login with admin-Campaign detail show role also, currently role showing only for a campaign manager

  5. Amaya API returns null if error instead of error and errorCode

  6. Hide metabase analytics

  7. Workflow rule configuration-on edit workflow, previously selected role getting save

  8. User - Assign Application - Workflow initiated - Workflow Approvals page displays User list in Grade type

  9. Pending Workflow -If the L1 approver is User List, then while clicking on the info icon, the popup does not show the user list. Also, it is " Grade List Details"

  10. Identity Hub- The pending initial login symbol is visible far away from the user name.

  11. On behalf configuration - While disabling and enabling the toggle, a popup message shows "This change will take effect on the user's next login" but it is getting reflected on the fly.

  12. On-behalf>Delegation- On behalf, mthe enu is not visible when logged in via the Delegatee account.

  13. SSO- Group mapping- Save button should be enabled when mandatory fields are filled

  14. Workflow- Even after updating the reporting manager as the 2nd level approver in the workflow, the 1st level approver is still being set at level 2

  15. Global search (Ctrl+K) - even if characters are not matching still shows suggestions

  16. The product menu getting hidden on the workflow page

  17. LDAP connector-LDAP SSL should be saved in Boolean in the DB

  18. User setting- An error message should be shown when any action is performed and when landing/refreshing the settings page

  19. User setting- External IDP rule is active-An admin user should not be able to lock a user when the external IDP rule matches the user condition

  20. Schedule history-ad by default today filter for from and to

  21. Teams config- When the view button is clicked, the user is still able to check or uncheck the boxes

  22. Menu action- Displaying an error message when a user already has one role assigned and tries to assign a menu action.

  23. Custom Attribute-Provision- When a custom attribute with special characters is created and applied in a provision rule (for user creation), the provision rule fails to trigger after the user is created.

  24. Lifecycle Management - All menus - The discard button is not working as expected.

  25. Application - SSO While saving the same config in two applications, while clicking on Edit SP config, a popup showing do you want to continue editing the SP configuration? But only the continue button is given.

  26. Application - SSO - While saving the configuration in a new application, the save button loader is loading continuously

  27. Amaya- Rename all operations(Test, Search, Sync, etc....) in sentence case

  28. Group Policy map- For group custom attribute Cymmetri field type should be automatically selected as working in the user custom field

  29. Teams config - while removing the condition in Group condition, shows the error " Please try again"

  30. On Behalf config - while removing the condition in Group condition, shows the error " Please try again"

  31. Teams Config - If the condition is kept blank and save is clicked, getting the error " Please try again"

  32. On behalf config- If the condition is kept blank and save is clicked, getting the error " Please try again"

  33. Import/Export- Showing error message when importing the file into a new tenant (AD specific)

  34. Import application-show error message user or groupwise

  35. Import application- Showing an error message when importing an Amaya-based application if the exported application was without the policy map checked

  36. Import/Export - When any application configuration is imported into a new tenant, the user should be redirected to the application provisioning page after the upload

  37. Amaya Azure- Showing route issue error message

  38. Import/Export Application- Convertor field types in the policy map are not getting imported

  39. Import/Export- Recon is not working for AD's new application bundle

  40. Workflow- When workflow over workflow is applied 2nd level approver is not getting updated

  41. Workflow- Even after updating Grade as the 2nd level approver in the workflow, the 1st level approver is still being set at level 2

  42. Workflow- After updating the user list as the 2nd level approver in the workflow, the 1st level approver is still being set at level 2

  43. Workflow- When the level 3 approver is updated in the workflow, a 'Workflow Not in Range' error message is displayed.

  44. Workflow TAT- Workflow is getting aborted when workflow approver is assigned to the user list

  45. Team config - Create - Discard button issue - After clicking not able to add the details in the condition section

  46. Import/Export- By default, the time in the application name should be removed when exported

  47. Rule engine- Remove the "above" word from the note

  48. login with admin-Campaign detail show role also, currently role showing only for a campaign manager

  49. Hide metabase analytics

  50. Error in the server log-authsrvc, No impact on the functional flow

  51. AD new application- User list is not getting displayed showing urersrvc unknown error.

  52. The campaign not ending, for tenant 2711

  53. Workflow rule configuration-on edit workflow, previously selected role getting save

  54. AD application new bundle - When SAMaccount name is set to false in the Group policy map, members are not assigned to the group when recon Pull is executed for both exist=Update

  55. My workspace> Inbox- When workflow assignment is reassigned by admin, then the previous approver should not be able to accept or reject the request if the page is already open in the previous approver account.

  56. After the campaign workflow triggered on revoked, even though the campaign had ended and the workflow was approved, applications were still getting unassigned.

  57. Workflow TAT- Workflow is getting aborted when grade is set at second level approver and set TAT time is over

  58. Workflow TAT- Workflow is getting aborted when 2 level approver is set and set TAT time is over

  59. Workflow TAT- Showing error when the user is not present and TAT is over

  60. Workflow TAT- Showing unauthorized error when TAT is over and operation is getting aborted

  61. User - Assign Application - Workflow initiated - Workflow Approvals page displays User list in Grade type

  62. Reports- SSO-based application- Reports are blank/ not showing data when SSO-based applications are accessed

  63. Pending Workflow -If the L1 approver is User List, then while clicking on the info icon, the popup does not show the user list. Also, it is " Grade List Details"

  64. AD new bundle>Group- When the "Sam account name" update checkbox is unchecked and the user attempts to update the description, the description does not get updated in the AD

  65. Import/ Export- When a file is exported from a different env (Dev) and imported to QA env, then credentials are also imported along

  66. Identity Hub- The pending initial login symbol is visible far away from the user name

  67. On behalf configuration - While disabling and enabling the toggle, a popup message shows "This change will take effect on the user's next login" but it is getting reflected on the fly.

  68. In the User creation workflow, L1 - User List approved, L2 - reporting manager after TAT is expired, the request is not getting auto reject.

  69. On-behalf>Delegation- On behalf menu is not visible when logged in via Delegatee account

  70. Import Manager-Manager is deleted and the user trying to assign them in the import history shows success but the audit shows a failed

  71. Application delete-Campaign-Deleted application available for review

  72. AD new bundle- User policy map- When Sam account name is mapped with any attribute and update checkbox is kept false, and the user is updated, the audit log shows a failed

  73. Workflow>Inbox- Address field names in inbox /pending workflow and identity hub users are not the same

  74. SSO- Group mapping- Save button should be enabled when mandatory fields are filled

  75. Campaign-email report showing error

  76. deployment_analytics_1 Service CPU utilization is 100%

  77. Application - Form - When submitted as blank, after assigning the application page is getting blank.

  78. Reports- Records are displayed after 11min approximately

  79. CSV Import users- An error message is not shown when the user is unable to save user details if space is included in the email

  80. After the campaign workflow was triggered on revoked, even though the campaign had ended and the workflow was approved, applications were still getting unassigned.

  81. User Workflow - If the reporting manager is set as 2 level approver, the reporting manager is showing as Unknown

  82. Workflow>Inbox- Address field names in inbox /pending workflow and identity hub users are not the same.

  83. Export- Rename Config type to Select All

  84. MFA- When the default MFA rule is inactive, the user can delete the default rule as well

  85. Amaya connector>Policy mapping- The bottom slider should be fixed

  86. Amaya || Validation preventing usage of long valid header

  87. Amaya Connector- By default only green colored (confirmed policy attributes) should be checked

  88. Amaya Quick Setup- When an auto test run fails and operations are manually updated, clicking 'Generate Policy Mapping' should exit the page.

  89. Application delete-Campaign-Deleted application available for review

  90. Import Manager-Manager is deleted and the user trying to assign them in the import history shows success but the audit shows a failed

  91. Import/Export- By default, the time in the application name should be removed when exported

  92. SSO - OpenID - Configure CIDR - Add - While clicking on the Add icon without entering any details, blank data is getting added.

  93. SSO - OpenID - Configure CIDR - While clicking on the delete icon, no message is displayed and the entry is removed

  94. Workflow List - View - Showing label as "Custom Workflow "

  95. Import/ Export- Application name while importing file should be limited to 50 characters

  96. Application - SSO - SLO toggle enable/disable audit log

  97. SOD; policies-Policy owner name is not getting updated after updating the user name from the Identity hub and without the owner name policy is getting saved

  98. AD new bundle- When recon is executed for both existing updates but the application is not linked, still user is still getting updated.

  99. Application - Form - When submitted as blank, after assigning the application page is getting blank.

  100. Masters - Grade- While clicking on the Add button it shows showing edit page of an existing record

  101. Tenant registration- Showing suspicious popup box when clicked on verify your email

  102. New tenant registration- If the tenant is already on the registration page then after clicking verify email from the mail box should show tenant is already registered

  103. Tenant registration- Taking time to register the tenant

  104. Email verification - The email verification link redirects to the otp verification screen.

  105. My Workflow> Teams- Add a short menu button

  106. Tenant creation not working

  107. After release v 3.1.2, for old updated tenant campaign module is disabled

  108. Portal-For module update showing error, already exist

  109. Push and FIDO scan zoom functionality not available at the time of Device MFA

  110. Push and FIDO scan zoom functionality not available at the time of application MFA

  111. User setting- The external IDP rule is active-An admin user should not be able to reset the user password when the external IDP rule matches the user condition

Known Bugs

  1. Manager notification: receiving user name required manager name

  2. Unable to identify application properties data type where value is empty

  3. Amaya || Create user operation fails due to an invalid password

  4. In forgot password/password breach condition-asking disabled MFA factor also

  5. Amaya-Autofill policy map, When the value is not present to the user at the time of application then Amaya passes "$." to the target

  6. Campaign - Reviewer can approve self review request

  7. After the campaign workflow was triggered on revoked, even though the campaign had ended and the workflow was approved, applications were still getting unassigned.

  8. Remote Group- AD Application- When users are removed from a remote group in Cymmetri, those members should also be removed from the group in the Active Directory

  9. Amaya- Client ID should be visible in encrypted form

  10. Provision Rule - While creating and configuring the custom attribute as "New ", the system is not initiating the rule.

  11. AD new bundle- When an AD application is assigned to a remote group, the application is highlighted in the background while assigning but disappears as soon as the application popup box is closed

  12. Reports- When the report is scheduled, Scheduler history shows content not found and the execution status is aborted.

  13. AD Application- When the Ad test provision fails, and the user tries to delete the application from a user account, then the application should go in a fail deletion state

  14. Audit- Taking time to load audit logs

  15. AD Application- Showing error when inserting start date in AD

  16. In the application setting if shown to the user flags off then the also application shows in recent applications.

  17. User lock- When a user account is active, and the same account is logged in through another browser, and by any means, the account gets locked, the first session should get terminated.

  18. Branding- When show Unlock link from branding is kept as No, and the admin user account gets locked, then the user is not able to unlock the account from the login page

  19. Application- When a user is adding /removing a role then it is not getting reflected without refreshing

  20. group push-not taking user in AD at the time of update

  21. Passwordless- WebAuthn; Showing not allowed error

  22. Delegation-On behalf: when login by the delegate and the on-behalf condition is not satisfied still shows othe n-behalf toggle button and gets removed when refreshed

  23. AD Application- Group name should not accept space while creating or updating group name

  24. Audit- Audi log should show log when the user is not getting any records in Recon history but showing task executed

Cymmetri Error Codes

A comprehensive list of all known Cymmetri error codes and their summary understanding:

ERROR CODE
ERROR TEXT

CONNECTION_ERROR

Unable to connect. Please check your connection and try again.

USRSRVC.LAST_DATE_REACHED

The application's request end date is greater than the user's end date.

USRSRVC.MISSING_DATES

Incorrect dates Please ensure the selected date range is proper.

USRSRVC.EXPIRED_TIME_BOUND

Access request duration has ended

REGSRVC.UNKNOWN

Error. Please try again later or contact Cymmetri Administrator.

REGSRVC.USER_NOT_FOUND

User not found.

REGSRVC.INVALID_TOKEN

Token expired. Try again.

REGSRVC.OTP_EXPIRED

OTP expired. Please resend and try again.

REGSRVC.OTP_LIMIT_EXCEED

Otp limit exceeded.

REGSRVC.INVALID_OTP

OTP does not match. Please check & try again

REGSRVC.INVALID_ARGUMENTS

Error. Please correct input and try again.

REGSRVC.INVALID_DOMAIN

Invalid Domain. Please try again.

REGSRVC.INVALID_CREDENTIALS

Invalid Credentials. Please try again.

REGSRVC.TERMS_AND_CONDITIONS_NOT_FOUND

Invalid Terms & Conditions. Please try again.

REGSRVC.INVALID_ACCOUNT_VERIFICATION_TOKEN

Invalid request. Contact Cymmetri administrator.

REGSRVC.DATA_IS_NOT_VALID

Invalid data. Please try again.

REGSRVC.PASSWORD_NOT_VALID

Invalid password. Please try again

REGSRVC.EMAIL_EXISTS

Duplicate Email Address. Please try again.

REGSRVC.DOMAIN_EXISTS

Duplicate Domain.

REGSRVC.DB_CONFIG_EXISTS

Database already exists. Contact Cymmetri administrator.

REGSRVC.USER_ALREADY_ACTIVE

User status is active. Contact Cymmetri administrator.

USRSRVC.MANAGER_NOT_FOUND

No Manager Found

USRSRVC.UNSUPPORTED_FILE_TYPE

Unsupported File Type

USRSRVC.UNKNOWN

Error. Please try again later or contact Cymmetri Administrator.

USRSRVC.INVALID_ARGUMENTS

Error. Please correct input and try again.

USRSRVC.NONUNIQUE_GROUPNAME

Group name already exists. Please try again.

USRSRVC.GROUPTYPE_NOT_FOUND

Group type not found. Contact Cymmetri administrator.

USRSRVC.OU_NOT_FOUND

Organization Unit not found. Please try again.

USRSRVC.PARENTGROUP_NOT_FOUND

Parent Group not found. Please try again.

USRSRVC.GROUP_NOT_FOUND

Group not found. Please try again.

USRSRVC.USER_NOT_FOUND

User not found. Please try again.

USRSRVC.CYCLIC_UPDATE

Operation not allowed for current input.

USRSRVC.INHERITED_GROUP

Operation not allowed for current input.

USRSRVC.USERTYPE_NOT_FOUND

User type not found. Please try again.

USRSRVC.EXISTING_MOBILE

User mobile number in use. Please try again.

USRSRVC.EXISTING_EMAIL

User email address in use. Please try again.

USRSRVC.DEPARTMENT_NOT_FOUND

Department not found. Please try again.

USRSRVC.DESIGNATION_NOT_FOUND

Designation not found. Please try again.

USRSRVC.COUNTRY_NOT_FOUND

Country not found. Please try again.

USRSRVC.EXISTING_LOGIN

User Login ID in use. Please try again.

USRSRVC.APPLICATION_NOT_FOUND

Application not found. Please try again.

USRSRVC.APPLICATION_ROLE_NOT_FOUND

Application role not found. Please try again.

PROVSRVC.CYMMETRI_LOGIN_FIELD_NOT_CONFIGURED

Please configure Cymmetri Login field for Policy Mapping.

PROVSRVC.APPLICATION_TEST_FAILED

Provision Configuration failed.

USRSRVC.USER_NOT_PROVISIONED

User not provisioned. Please try again.

USRSRVC.CHILD_GROUP_FOUND

Cannot Delete as Child group found.

USRSRVC.GROUP_HAS_ASSIGNED_APPS

Group has assigned applications. Remove and try again.

USRSRVC.USER_ASSIGNED_GROUP

Cannot delete as User assigned to group.

USRSRVC.USER_MUST_PRESENT_IN_TARGET

User must present in target system before assign it to group.

USRSRVC.INACTIVE_USER

Inactive User cannot perform this action.

USRSRVC.INVALID_MANAGER

Invalid manager.

USRSRVC.MIN_ORG_ADMIN_RULE_VIOLATION

Admin role cannot be removed for this user.

USRSRVC.USER_ROLE_MAPPING_EXISTS

Role Already Exists.

USRSRVC.APPLICATION_ROLE_ALREADY_ASSIGNED

Application role is already assigned.

USRSRVC.APPLICATION_ALREADY_ASSIGNED

Application is already assigned.

USRSRVC.USER_ROLE_MAPPING_NOT_EXISTS

User role mapping does not exists.

USRSRVC.CANNOT_REMOVE_PROVISIONED_APPLICATION

Cannot remove already provisioned application.

USRSRVC.EMPTY_FILE

Empty file uploaded.

USRSRVC.SELF_STATUS_CHANGE_NOT_ALLOWED

This user cannot be deleted.

USRSRVC.MANAGER_ASSIGNMENT_REJECTED

Error. The manager assignment is invalid.

USRSRVC.INVALID_ENDDATE

The end date should be greater than start date.

USRSRVC.SELF_ROLE_CHANGE_NOT_ALLOWED

Self role change is not allowed.

USRSRVC.CUSTOM_ATTRIBUTE_MASTER_EXIST

Custom attribute already exist.

USRSRVC.CUSTOM_ATTRIBUTE_MASTER_NOT_FOUND

Custom attribute not found.

USRSRVC.DUPLICATE_NAME

Duplicate name record already exist.

USRSRVC.DUPLICATE_LABEL

Duplicate label record already exist.

USRSRVC.ATTRIBUTE_RIGHTS_NOT_FOUND

Attribute rights not found.

USRSRVC.REMOTE_GROUP_APPLICATION_NOT_FOUND

Application must present before assign user to remote group.

USRSRVC.REMOTE_GROUP_NAME_NOT_MODIFIED_EXCEPTION

Remote group name not able to update

USRSRVC.EMPTY_LOGIN

Something went wrong Please contact the administrator.

USRSRVC.TOO_LARGE_FILE

File size should not be more than {size}

USRSRVC.FORM_DEACTIVATED_EXCEPTION

Form is inactive

USRSRVC.ACTION_NOT_SUPPORTED

This action is not supported

AUTHSRVC.ACCESS_DENIED

Invalid Credentials.

AUTHSRVC.TENANT_EXPIRED

Free trial expired. Please contact Cymmetri administrator.

AUTHSRVC.UNKNOWN

Please contact system administrator.

AUTHSRVC.INVALID_TOKEN

Token is invalid.

AUTHSRVC.USER_NOT_FOUND

User not found.

AUTHSRVC.CANT_SET_FALSE_DEFAULT_PASSWORD_POLICY

Default password policy cannot be false.

AUTHSRVC.CONNECTION_FAILED

Connection failed.

AUTHSRVC.CANT_DELETE_DEFAULT_PASSWORD_POLICY

Cannot delete default password policy.

AUTHSRVC.INVALID_ARGUMENTS

Invalid argument.

AUTHSRVC.INVALID_AUTH_POLICY_CONFIG

Invalid auth policy config.

AUTHSRVC.ACCESS_DENIED_TOKEN

Session expired. Please login again

AUTHSRVC.ADAPTIVE_BLOCK_ACTION

Action blocked. Please contact administrator.

SESSION_EXPIRED

Session expired. Please refresh and try again

AUTHSRVC.NON_REMOVABLE_REFERENCED_ENTITY

Cannot modify IDP configuration till active under Authentication Policy.

AUTHSRVC.PASSWORD_POLICY_NAME_ALRAEDY_EXISTS

Password policy name already exists.

AUTHSRVC.PASSWORD_POLICY_CONDITION_ALRAEDY_EXISTS

Policy Conditions already exists.

AUTHSRVC.DEFAULT_POLICY_UPDATE_NOT_ALLOWED

Default password policy update not allowed.

AUTHSRVC.PASSWORD_COMPOSITION_RULE_VIOLATION

Password provided does not match the required guidelines.

AUTHSRVC.MOBILE_NOT_FOUND

Mobile number is not registered please contact Cymmetri Administrator.

AUTHSRVC.ALREADY_EXISTS

Name already exist. Please enter unique name.

AUTHSRVC.LDAP_ACCESS_DENIED

Access denied.

AUTHSRVC.CLIENT_EXISTS

API Client with same name already configured.

AUTHSRVC.USER_NOT_ACTIVE

Delegated user not active

AUTHSRVC.INVALID_AUTH_CONFIG

Invalid auth config

AUTHSRVC.PASSWORD_POLICY_NAME_ALREADY_EXISTS

Password policy name already exists.

AUTHSRVC.TRUST_DEVICE_MAX_DEVICE_EXCEPTION

Exceeded device trust max limit

AUTHSRVC.TRUST_DEVICE_EXPIRY_EXCEPTION

Exceeded expiration time for trust devices

AUTHSRVC.MULTIPLE_TRUST_DEVICE_CONFIG

Multiple trust device configuration found

AUTHSRVC.INVALID_GLOBAL_SESSION_CONFIGURATION

Invalid global auth configuration

AUTHSRVC.MULTI_SESSION_ACCESS_DENIED

Session(s) already in progress. Logout from all sessions to continue.

MFASRVC.UNKNOWN

Error. Please try again.

MFASRVC.USER_NOT_FOUND

User not found. Please try again.

MFASRVC.ALREADY_SENT_SMS_OTP

SMS OTP already sent.

MFASRVC.INVALID_SMS_OTP

Invalid SMS OTP provided.

MFASRVC.RESEND_COUNT_EXCEED

Allowed resend attempt exceed please try after some time

MFASRVC.PUSH_NOTIFICATION_FAILED

Failed to send the push notification. Please try again later or contact Cymmetri Administrator.

MFASRVC.MFA_CONFIG_NOT_FOUND

Multi Factor Authentication configuration not found.

MFASRVC.INVALID_ARGUMENTS

Error. Invalid request.

MFASRVC.QUESTION_NOT_FOUND

Question not found.

MFASRVC.DUPLICATE_QUESTION

Question field is duplicate. Please try again.

MFASRVC.INCORRECT_ANSWER

Answer field is incorrect. Please try again.

MFASRVC.INVALID_USERID

Invalid User. Please try again.

MFASRVC.INVALID_QUESTIONID

Question is invalid. Please try again.

MFASRVC.USER_NOT_REGISTERED

User is not registered for TOTP/Push Authentication

MFASRVC.EMPTY_QUESTION

Question field is empty. Please try again.

MFASRVC.FAILED_MINIMUM_CORRECT_ANSWER

Please provide correct answer for each question.

MFASRVC.INVALID_TOTP

Invalid Time based OTP provided.

MFASRVC.INVALID_ANSWER

Answer field is invalid. Please try again.

MFASRVC.QUESTION_NOT_REGISTERED

Question is not registered.

MFASRVC.NON_REMOVABLE_QUESTION

Question in use and cannot be removed.

MFASRVC.USER_RESPONSE_PENDING

User response is pending.

MFASRVC.USER_DENIED_ACCESS

User denied access.

MFASRVC.NOT_ABLE_TO_MODIFY

Not able to modify. Please try again

MFASRVC.INVALID_ANSWER_LENGTH

Invalid answer length

MFASRVC.DISPOSABLE_EMAIL

MFASRVC.FIREHOL_IP_REPUTATION

Ip reputation sync failed

MFASRVC.SYNC_PROCESS_RUNNING

Sync is in progress. Please wait

MFASRVC.IMPOSSIBLE_TRAVEL_NOT_FOUND

Config not found

MFASRVC.DEVICE_TRUST_NOT_FOUND

Config not found

MFASRVC.BLACKLISTED_LOCATION_NOT_FOUND

Config not found

MFASRVC.LOCATION_EMPTY

MFASRVC.BLACKLISTED_IP_NOT_FOUND

Blacklisted IP not found

MFASRVC.IP_ADDRESS_EMPTY

MFASRVC.MFA_NOT_FOUND

MFA not found

MFASRVC.INVALID_CONFIG

Invalid configuration

MFASRVC.SERVICE_NOT_SUPPORTED

MFASRVC.PLUGIN_REGISTRY_NOT_REGISTERED

MFASRVC.BLACKLISTED_IPADDRESS_CONFIG_NOT_FOUND

Config not found

MFASRVC.BLACKLISTED_LOCATION_CONFIG_NOT_FOUND

Config not found

MFASRVC.IMPOSSIBLE_TRAVEL_CONFIG_NOT_FOUND

Config not found

MFASRVC.BREACHED_PASSWORD_CONFIG_NOT_FOUND

Config not found

MFASRVC.COUNTRY_CODE_MISMATCH_CONFIG_NOT_FOUND

Config not found

MFASRVC.SHORT_LIVED_DOMAIN_CONFIG_NOT_FOUND

Config not found

MFASRVC.USER_BEHAVIOUR_CONFIG_NOT_FOUND

Config not found

MFASRVC.MULTIPLE_DEVICE_TRUST_FOUND

Multiple config found

MFASRVC.COMMON_CREDENTIAL_DOWNLOAD_FAILED

WKFLSRVC.UNKNOWN

Please contact system Administrator

WKFLSRVC.WORKFLOW_NOT_FOUND

No workflow available

WKFLSRVC.INVALID_ARGUMENTS

Please check input and try again.

WKFLSRVC.INVALID_LEVEL

Workflow Config issue

WKFLSRVC.EXCEEDED_REPORTING_MANAGER

Can not more than reporting manager

WKFLSRVC.WORKFLOW_SETUP_NOT_FOUND

No workflow config available

WKFLSRVC.REQUESTOR_NOT_FOUND

Requestor not found in the system.

WKFLSRVC.WORKFLOW_IN_PROGESS

Request is pending for approval.

WKFLSRVC.REPORTING_MANAGER_NOT_FOUND

Please assign approver's manager to complete workflow.

WKFLSRVC.LEVEL_NOT_IN_RANGE

Workflow level is not in range.

WKFLSRVC.WORKFLOW_SETUP_ALREADY_EXISTS

Workflow setup already exists.

WKFLSRVC.COMMON_REQ_ASSG_ID

Self-approval is not allowed Please contact the administrator for the reassignment.

WKFLSRVC.SAME_REQUESTOR_ASSIGNEE

Workflow cannot be assigned to same user.

WKFLSRVC.WORKFLOW_ALREADY_EXISTS

Workflow with same name already exists.

WKFLSRVC.DAYS_THRESHOLD_EXCEED_EXCEPTION

Max allowed TAT is {maxAllowedDays} days

WKFLSRVC.DELEGATE_COMMON_REQ_ASSG_ID

Approver and assignee can't be same.

WKFLSRVC.APPLICATION_DECOMMISSIONED

This application is decommissioned so the request can not be approved/rejected please refresh the page.

SSOCONFIGSRVC.UNKNOWN

Error. Please try again.

SSOCONFIGSRVC.SSO_CONFIG_NOT_FOUND

SSO config not found.

SSOCONFIGSRVC.SAML_CONFIG_NOT_FOUND

Saml config not found.

SSOCONFIGSRVC.OPENID_CLIENT_NOT_FOUND

OpenID config not found.

SSOCONFIGSRVC.DUPLICATE_OPENID_CLIENT_ID

Duplicate OpenID Client ID.

SSOCONFIGSRVC.API_CONFIG_NOT_FOUND

API config not found.

SSOCONFIGSRVC.INVALID_ARGUMENTS

Invalid Arguments.

SSOCONFIGSRVC.INVALID_CIDR

Not all CIDR are valid

SSOCONFIGSRVC.UNSUPPORTED_FILE_TYPE

Unsupported File Type

SSOCONFIGSRVC.ERROR_GENERATING_KEYS

Failed to generate keys.

SSOCONFIGSRVC.CERTIFICATE_PARSING_ERROR

Failed to read certificate. Please try again.

SSOCONFIGSRVC.ERROR_DEACTIVATING_KEYS

Failed to deactivate key. Please try again.

SSOCONFIGSRVC.KEY_GENERATION_FAILED

Failed to generate keys.

SSOCONFIGSRVC.METADATA_GENERATION_FAILED

Could not generate Metadata.

SSOCONFIGSRVC.ALRAEDY_EXISTS

Configuration for same Entity ID already exists.

SSOCONFIGSRVC.KEYS_CANNOT_BE_DISABLED

Key is being used in IDP or SP

SSOCONFIGSRVC.KEY_DOES_NOT_EXISTS

No related key found

SSOCONFIGSRVC.IDENTITY_PROVIDER_IS_DISABLED

Identity Provider is disabled

SSOCONFIGSRVC.DUPLICATE_POLICY_MAPPING

Policy mapping already exists

SSOCONFIGSRVC.USER_DOES_NOT_HAVE_ACCESS

User does not have access

SSOCONFIGSRVC.KEYS_IS_DISABLED

Keys Disabled

SSOCONFIGSRVC.IDENTITY_PROVIDER_DOES_NOT_EXISTS

Identity Provider does not exist

SSOCONFIGSRVC.IDENTITY_PROVIDER_KEY_IS_DISABLED

Identity Provider key disabled

SSOCONFIGSRVC.SERVICE_PROVIDER_IS_DISABLED

Service Provider disabled

SSOCONFIGSRVC.IDENTITY_PROVIDER_ALREADY_ENABLED

Identity Provider already enabled

SSOCONFIGSRVC.IDENTITY_PROVIDER_CANNOT_BE_DISABLED

Identity Provider can not be disabled

SSOCONFIGSRVC.KEYS_ALREADY_EXISTS

Keys already exists

SSOCONFIGSRVC.KEY_MINIMUM_EXPIRATION

Key Minimum expiration

SSOCONFIGSRVC.SERVICE_PROVIDER_ENABLED

Service provider enabled

SSOCONFIGSRVC.SERVICE_PROVIDER_DISABLED

Service provider disabled

SSOCONFIGSRVC.KEY_IS_BEING_USED

Key already used

SSOCONFIGSRVC.SERVICE_PROVIDER_CANNOT_BE_UPDATED

Service provider can not be updated

SSOCONFIGSRVC.SERVICE_PROVIDER_IS_BEING_USED

Service provider is being used

SSOCONFIGSRVC.INVALID_SAML_CONFIG

invalid saml configuration

SSOCONFIGSRVC.NOT_FOUND

SSO cofiguration not found

SSOCONFIGSRVC.CONNECTION_FAILED

SSO configuration connection failed

SSOCONFIGSRVC.FORBIDDEN

SSO configuration forbidden

SSOCONFIGSRVC.UNAUTHORIZED

SSO configuration unauthorized

SSOCONFIGSRVC.CERTIFICATE_EXPIRED

SSO configuration certificate is expired

SSOCONFIGSRVC.SAML_APP_CONFIG_NOT_FOUND

SSO configuration saml application configuration not found

SSOCONFIGSRVC.SAML_ATTR_CONFIG_NOT_FOUND

SSO configuration saml attribute configuration not found

SSOCONFIGSRVC.OPENID_SCOPE_NOT_FOUND

SSO configuration openid scope not found

SSOCONFIGSRVC.OPENID_CLAIM_NOT_FOUND

SSO configuration openid claim not found

SSOCONFIGSRVC.APPLICATION_NOT_FOUND

SSO configuration application not found

SSOCONFIGSRVC.DUPLICATE_POLICYATTRIBUTE

SSO configuration policy attribute is duplicate

SSOCONFIGSRVC.INVALID_POLICYATTRIBUTE_ID

SSO configuration policy attribute is invalid

SSOCONFIGSRVC.INAVLID_POLICYATTRIBUTE_APPLICATION

SSO configuration policy attribute application is invalid

SSOCONFIGSRVC.MANDATORY_ENTRY

SSO configuration policy field is mandatory

SSOCONFIGSRVC.INVALID_POLICY_MAP

SSO configuration policy map is invalid

SSOCONFIGSRVC.NO_MAPPING_FOUND

SSO configuration mapping is not found

SSOCONFIGSRVC.IDENTITY_PROVIDER_DOES_EXISTS

SSO configuration identity provider does not exist

SSOCONFIGSRVC.MULTIPLE_IDENTITY_PROVIDER_EXISTS

SSO configuration multiple identity provider exists

SSOCONFIGSRVC.SERVICE_PROVIDER_EXISTS

SSO configuration service provider already exists

SSOCONFIGSRVC.SERVICE_PROVIDER_DOES_NOT_EXISTS

Service provider does not exist

SSOCONFIGSRVC.DOMAIN_EXISTS

Domain doesn't exists

SAMLSRVC.KEY_DOES_NOT_EXISTS

Key doesn't exists

SAMLSRVC.INVALID_COOKIE

Invalid session. Re-login and try again

SAMLSRVC.IDENTITY_PROVIDER_IS_DISABLED

Identity Provider is disabled

SAMLSRVC.EXPIRED_TOKEN

Session Expired. Please re-login and try again

SAMLSRVC.KEYS_IS_DISABLED

Key is disabled

SAMLSRVC.KEYS_IS_EXPIRED

Key is expired

SAMLSRVC.KEYS_NOT_GENERATED

Public and private key is not generated

SAMLSRVC.SAML_TYPE_NOT_APPLICABLE

SAML type configured and SAML type received mismatched

SAMLSRVC.NAMEID_MISMATCH

SAML nameId configured and nameId received mismatched

SAMLSRVC.INVALID_SAML2_AUTHN_REQUEST_SIGNATURE

SAML authentication request signature is invalid

SAMLSRVC.ISSUE_INSTANT_MISMATCH

SAML authentication response is invalid with issue instant

SAMLSRVC.MESSAGE_REPLAY

SAML message is being sent again

SAMLSRVC.DESITNATION_MISMATCH

SAML destination configured and received mismatched

SAMLSRVC.VERSION_MISMATCH

SAML version does not match

SAMLSRVC.PROTOCOL_BINDING_MISMATCH

SAML protocol binding does not match

SAMLSRVC.REQUEST_ISSUER_URI_MISMATCH

SAML request issuer uri does not match

SAMLSRVC.ASSERTION_CONSUMER_SERVICE_URI_MISMATCH

SAML request assertion consumer service uri does not match

SAMLSRVC.INVALID_USER_SESSION

SAML user session is invalid

SAMLSRVC.USER_DOES_NOT_HAVE_ACCESS

User does not have access

SAMLSRVC.IDENTITY_PROVIDER_DOES_NOT_EXISTS

Identity Provider does not exist

SAMLSRVC.IDENTITY_PROVIDER_KEY_IS_DISABLED

Identity Provider key is disabled

SAMLSRVC.SERVICE_PROVIDER_IS_DISABLED

Service Provider is disabled

UTILSRVC.UNKNOWN

Error. Please try again.

UTILSRVC.INVALID_ARGUMENTS

Error. Please correct input and try again.

UTILSRVC.CONFIGURATION_EXIST

Hook already present.

UTILSRVC.ALREADY_EXISTS

Hook already present.

UTILSRVC.META_ATTRIBUTE_EXISTS

Name/Key or Value already exist.

UTILSRVC.MODULES_ENQUIRY_EXIST

Sales team is working on your request. We will get back to you soon.

UTILSRVC.LABEL_ALREADY_EXIST

Label Already Exists

UTILSRVC.EVENT_ALREADY_EXIST

Event Already Exists

UTILSRVC.BEHALF_CONFIG_NOT_FOUND

On Behalf configuration is not found.

UTILSRVC.MULTIPLE_BEHALF_CONFIG_FOUND

Multiple Behalf configurations found.

UTILSRVC.LENGTH_EXCEED_EXCEPTION

Length exceeded

UTILSRVC.SCRIPT_CUSTOM_ERROR-MOBILEALREADYEXIST

Mobile number already in use Try again with another number.

UTILSRVC.SCRIPT_CUSTOM_ERROR-EMAILALREADYEXIST

Email already in use Try again with another email.

USRSRVC.FORM_NOT_FOUND

Form not found

UTILSRVC.WEBHOOK_CALL_FAILED

Webhook test failed.

UTILSRVC.BATCH_TASK_EXECUTION_FAILED

Batch process execution failed.

UTILSRVC.BATCH_TASK_ALREADY_EXIST

Batch task already exists.

PROVSRVC.UNKNOWN

Error. Please try again later or contact Cymmetri Administrator.

PROVSRVC.USER_NOT_FOUND

User not found.

PROVSRVC.INVALID_ARGUMENTS

Error. Please correct input and try again.

PROVSRVC.APPLICATION_NOT_FOUND

Application not found. Please try again.

PROVSRVC.INVALID_USER_ACTION

User action not allowed. Please check configuration.

PROVSRVC.INVALID_GROUP_ACTION

Group action not allowed. Please check configuration.

PROVSRVC.INVALID_ROLE_ACTION

Role action not allowed. Please check configuration.

PROVSRVC.INAVLID_ACTION

Error. Please try again.

PROVSRVC.UID_NOT_FOUND

Record not found. Please try again.

PROVSRVC.Empty_Role_Id

Role not provided. Please try again.

PROVSRVC.Duplicate_GroupID

Duplicate Group association.

PROVSRVC.Invalid_GroupId

Invalid Group association.

PROVSRVC.CONNECTOR_NOT_FOUND

Connector not available. Please contact Cymmetri administrator.

PROVSRVC.UNSUPPORTED_OPERATION

Operation not supported.

PROVSRVC.APPLICATION_ALREADY_EXISTS

Application already exists.

PROVSRVC.INVALID_POLICYATTRIBUTE_ID

Invalid Policy configuration. Please try again.

PROVSRVC.DUPLICATE_POLICYATTRIBUTE

Duplicate Policy attribute selected.

PROVSRVC.INVALID_POLICY_MAP

Invalid Policy map.

PROVSRVC.INVALID_MASTER_AAPPLICATION_Id

Invalid master application reference.

PROVSRVC.NO_MAPPING_FOUND

Policy map not found.

PROVSRVC.DUPLICATE_POLICY_MAPPING

Duplicate Policy mapping.

PROVSRVC.INAVLID_POLICYATTRIBUTE_APPLICATION

Invalid Policy association. Please try again.

PROVSRVC.PROVISIONING_NOT_ENABLE

Provisioning not enable

PROVSRVC.DUPLICATE_ROLE

Role ID in use. Please try again.

PROVSRVC.DUPPLICATE_NAME

Name already in use.

PROVSRVC.IDENTITY_ALREADY_EXISTS_EXCEPTION

User principle is already checked Please reset and try again.

PROVSRVC.IDENTITY_NOT_CHECKED_EXCEPTION

At least one user principle should be checked.

RULESRVC.UNKNOWN

Error. Please try again.

RULESRVC.RULE_NOT_FOUND

Rule not found.

RULESRVC.RULE_CONDITION_NOT_FOUND

Rule condition not found.

RULESRVC.RULE_ACTION_GROUP_NOT_FOUND

No group associated with rule. Please try again.

RULESRVC.NON_REMOVABLE_REFERENCED_ENTITY

Cannot be modified as entity in use.

RULESRVC.ALRAEDY_EXISTS

Rule with same name already exists.

RULESRVC.RULE_CONFIGURE_ALREADY_EXIST

Rule with same condition configuration already exists.

RULESRVC.MULTIPLE_ZONES_FOUND

Multiple zones found.

RULESRVC.ZONE_NOT_FOUND

Zone not found.

RULESRVC.INVALID_ARGUMENTS

Please correct the input and try again.

RULESRVC.DEFAULT_RULE_NOT_FOUND

Default rule not found.

IGSRVC.UNKNOWN

Error. Please try again.

IGSRVC.INVALID_JWT

Error. Invalid JWT token.

IGSRVC.CAMPAIGN_COMPLETION_PERIOD_EXCEED

Error. Campaign Completion Period Exceeded.

IGSRVC.CAMPAIGN_STAGE_NOT_FOUND

Error. Campaign Stage Not Found.

IGSRVC.CAMPAIGN_SCOPE_NOT_FOUND

Error. Campaign Scope Not Found.

IGSRVC.CAMPAIGN_ALREADY_IN_DRAFT_STATE

Error. Campaign Already In Draft State.

IGSRVC.CAMPAIGN_ALREADY_IN_PUBLISHED_STATE

Error. Campaign Already In Published State.

IGSRVC.CAMPAIGN_EXECUTION_IN_PROGRESS

Error. Campaign Execution in Progress.

IGSRVC.CAMPAIGN_ASSIGNMENT_NOT_FOUND

Error. Campaign Assignment Not Found.

IGSRVC.CAMPAIGN_HISTORY_NOT_FOUND

Error. Campaign History Not Found.

IGSRVC.UNABLE_TO_PROCESS_RESPONSE

Error. Unable To Process Response.

IGSRVC.CAMPAIGN_ASSIGNMENT_APPLICATION_NOT_FOUND

Error. Campaign Assignment Application Not Found.

IGSRVC.CAMPAIGN_ASSIGNMENT_APPLICATION_ROLE_NOT_FOUND

Error. Campaign Assignment Application Role Not Found.

IGSRVC.APP_ROLE_ALREADY_PROCEED

Error. App Role Already Proceeded.

IGSRVC.INACTIVE_USER_FOUND

Error. Inactive User Found.

IGSRVC.NO_ACTIVE_EXECUTION_FOUND

Error. No Active Execution Found.

IGSRVC.INVALID_CRON_EXPRESSION

Error. Invalid Cron Expression.

IGSRVC.DUPLICATE_CAMPAIGNNAME

Error. Duplicate Campaign Name.

IGSRVC.CAMPAIGN_NOT_FOUND

Campaign not found.

IGSRVC.INVALID_ARGUMENTS

Error. Please correct input and try again.

IGSRVC.CAMPAIGN_STATE_STARTED

Error. Campaign State Already Started.

IGSRVC.STAGE_LIMIT_EXCEED

Error. Stage Limit Exceeded.

IGSRVC.DUPLICATE_STAGE

Error. Duplicate Stage.

IGSRVC.ASSIGNMENT_ALREADY_PROCEED

Error. Assignment Already Proceeded.

IGSRVC.INVALID_CAMPAIGN_ITERATION

Invalid Campaign Iteration.

IGSRVC.INVALID_CAMPAIGN_MANAGER_ASSIGNEE

Campaign manager or assignee configured in stages are not valid.

IGSRVC.INVALID_CAMPAIGN_STATUS

Campaign execution in progress operation not allowed.

IGSRVC.USER_WITH_NO_VALID_APPLICATION

No valid assignments found aborted execution.

IGSRVC.CONNECTION_FAILED

Please check your internet connection.

IGSRVC.ALRAEDY_EXISTS

Record already exists.

IGSRVC.FORBIDDEN

Please contact system administrator.

IGSRVC.UNAUTHORIZED

Please contact system administrator.

IGPROCESS.UNKNOWN

Error. Please try again.

IGPROCESS.INVALID_ARGUMENTS

Error. Please correct input and try again.

IGPROCESS.CAMPAIGN_NOT_FOUND

Error. Campaign Not Found.

IGPROCESS.NO_ACTIVE_EXECUTION_FOUND

Error. No Active Execution Found.

IGPROCESS.CAMPAIGN_HISTORY_NOT_FOUND

Error. Campaign History Not Found.

IGPROCESS.INVALID_CAMPAIGN_ITERATION

Error. Invalid Campaign Iteration.

IGPROCESS.CAMPAIGN_EXECUTION_IN_PROGRESS

Error. Campaign Execution In Progress.

IGPROCESS.MATCHING_ASSIGNMENTS_NOT_FOUND

Error. Matching Assignments Not Found.

SCHEDULER.UNKNOWN

Error. Please try again.

SCHEDULER.TASK_NOT_FOUND

Error. Task Not Found.

SCHEDULER.TASK_NOT_ACTIVE

Error. Task Not Active.

SCHEDULER.INVALID_ARGUMENTS

Error. Please correct input and try again.

SCHEDULER.INVALID_START_DATE

Error. Invalid Start Date.

SCHEDULER.TENANT_NOT_FOUND

Error. Tenant Not Found.

SCHEDULER.UPDATE_NOT_SUPPORTED

Error. Update Is Not Supported.

SCHEDULER.CRON_REPETITION_BELOW_ALLOWED_LIMIT

Error. Cron Repetition Is Below Allowed Limit.

SCHEDULER.INVALID_CRON_EXPRESSION

Invalid Cron Expression.

SODSRVC.ALREADY_EXISTS

Error. Value Already Exists.

SODSRVC.INVALID_ARGUMENTS

Error. Please correct the input and try again.

SAMLEXTIDPCONFIGSRVC.UNKNOWN

Error. Please try again.

SAMLEXTIDPCONFIGSRVC.IDENTITY_PROVIDER_WITH_NAME_EXISTS

Idenity Provider with same name already exist. Please enter unique name.

SAMLEXTIDPCONFIGSRVC.SERVICE_PROVIDER_WITH_NAME_EXISTS

Service Provider with same name already exists.

SAMLEXTIDPCONFIGSRVC.NON_REMOVABLE_REFERENCED_ENTITY

Cannot modify or remove service provider till active under external identity policy or rule.

SAMLEXTIDPCONFIGSRVC.INVALID_ARGUMENTS

Please correct the input and try again.

SAMLEXTIDPCONFIGSRVC.CERTIFICATE_PARSING_ERROR

Error occurred while parsing certificate.

SAMLEXTIDPCONFIGSRVC.AUTH_TYPE_CANNOT_BE_UPDATED

Identity provider type cannot be updated.

SAMLEXTIDPCONFIGSRVC.CONNECTION_FAILED

Please check your internet connection.

SAMLEXTIDPCONFIGSRVC.IDP_CONFIGURATION_NOT_FOUND

Identity provider configuration not found.

SAMLEXTIDPCONFIGSRVC.MULTIPLE_IDP_CONFIGURATION_FOUND

Multiple identity provider configuration found.

SAMLEXTIDPCONFIGSRVC.NAME_ID_POLICY_NAME_ID_VALUE_MISMATCH

NameIdPolicy and NameIdValue does not match.

SAMLEXTIDPCONFIGSRVC.SP_CONFIGURATION_NOT_FOUND

Service provider configuration not found.

SAMLEXTIDPCONFIGSRVC.UNAUTHORIZED

Please contact system administrator.

SAMLEXTIDPCONFIGSRVC.SERVICE_PROVIDER_NOT_FOUND

Service provider not found.

SAMLEXTIDPCONFIGSRVC.CERTIFICATE_NOT_FOUND

Certificate not found.

SAMLEXTIDPCONFIGSRVC.EAMIL_EXISTS

Email already exists.

SAMLEXTIDPCONFIGSRVC.CUSTOM_IDENTITY_TYPE_MUST_HAVE_ID

Custom identity type must have ID.

SAMLEXTIDPCONFIGSRVC.INACTIVE_CONFIGURATION_FOUND

Inactive configuration found.

SAMLEXTIDPCONFIGSRVC.INVALID_IDP_CONFIGURED

Invalid IDP configured.

SAMLEXTIDPCONFIGSRVC.NO_MAPPING_FOUND

No mapping found.

SAMLEXTIDPCONFIGSRVC.INVALID_POLICY_MAPPING

Invalid policy mapping.

SAMLEXTIDPCONFIGSRVC.POLICY_MAP_REQUIRED_FIELD_NOT_FOUND

Policy map required field not found.

SAMLEXTIDPCONFIGSRVC.MANDATORY_FIELD_EXCEPTION

Mandatory field exception.

SAMLEXTIDPCONFIGSRVC.MAPPING_ALREADY_EXISTS

Mapping already exists.

SAMLEXTIDPCONFIGSRVC.JIT_CONFIGURATION_NOT_FOUND

JIT configuration not found.

USRSRVC.INVALID_EXTENSION_ENDDATE

Extended end date should be less than current access end date.

MFASRVC.SMS_OTP_EXPIRED

SMS OTP expired.

MFASRVC.SHORT_ANSWER_LENGTH

Answer length is short.

MFASRVC.DEVICE_INFO_NOT_FOUND

Please scan the QR code.

AUTHSRVC.USER_LOCKED

User locked. Please Unlock your Account.

AUTHSRVC.EMAIL_NOT_FOUND

Email not found.

AUTHSRVC.INVALID_USER_ACCOUNT_STATE

Your account is expired/inactive. Please contact Cymmetri Administrator

AUTHSRVC.INVALID_DATE

Start/End date should be greater than current date and time.

AUTHSRVC.DELEGATE_CONSENT_NOT_FOUND

Error. Delegate consent not found.

AUTHSRVC.DELEGATE_USER_NOT_FOUND

Error. User doesn't have delegation access.

AUTHSRVC.NO_OPTION_AVAILABLE

Please contact Cymmetri Administrator for Password Reset.

AUTHSRVC.DELEGATION_DEACTIVATE

Error. Delegation is inactive.

AUTHSRVC.PASSWORD_EXPIRED

Your password has expired Please reset your password.

PROVSRVC.UNSUPPORTED_DELEGETE_MFA_SETUP

Delegatee can't setup MFA for application having additional authentication

PAMSRVC.UNSUPPORTED_DELEGETE_MFA_SETUP

Delegatee can't setup MFA for application having additional authentication

SLFSRVC.EXISITNG_APP_IN_TAG_FOUND

Application already available in tag.

AD-ADAPTER.FAILED_TO_PWD_CHANGE

Password change failed.

AUTHSRVC.INVALID_CONFIG

Invalid config for authentication policy or rule

PROVSRVC.UNAUTHORIZED

Unauthorized access.

REGSRVC.UNAUTHORIZED

Unauthorized access.

MFASRVC.INVALID_MFA_OTP_CONFIG

Invalid Otp config please contact admin

MFASRVC.EMAIL_NOT_FOUND

Email not registered please contact admin

MFASRVC.MOBILE_NOT_FOUND

Mobile not registered please contact admin

MFASRVC.EMAIL_MOBILE_NOT_FOUND

Mobile or email not registered please contact admin

MFASRVC.LARGE_ANSWER_LENGTH

Maximum answer lenght exceeded try with shorter length answer

SLFSRVC.EXISITNG_USER_TAG_FOUND

Tag with same name already exists

SLFSRVC.IMAGE_MAXSIZE_EXCEEDED

Maximum limit for file size exceeded.

SLFSRVC.IMAGE_TYPE_NOTALLOWED

Image Type not allowed

SLFSRVC.INVALID_ARGUMENTS

Invalid Arguments

REPORT.EMAIL_NOT_EXISTS_EXCEPTION

User Email Not Found. Please contact cymmetri administrator.

REPORT.CONNECTION_FAILED

Failed to send report.

SOME_ERROR_OCCURRED_WORKING_ON_IT

Please contact cymmetri administrator.

INVALID_IDENTITY_PROVIDER_STATUS

Invalid Identity Provider Status. Please contact cymmetri administrator.

INVALID_ARGUMENTS

Please correct Input and try again. Please contact cymmetri administrator.

INVALID_SERVICE_PROVIDER_STATUS

Invalid Service Provider Status. Please contact cymmetri administrator.

MANDATORY_FIELD_EXCEPTION

Mandatory Field is Missing. Please contact cymmetri administrator.

TENANT_OR_HOST_NOT_RECEIVED_FROM_NGINX

Please contact cymmetri administrator.

TENANT_OR_HOST_PROTO_NOT_RECEIVED_FROM_NGINX

Please contact cymmetri administrator.

SOME_IMPERSONATE_ACCESS

Unauthorized Access. Please contact cymmetri administrator.

SERVICE_PROVIDER_INBOUND_MESSAGE_ERROR

Invalid SAML Message Received. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_ASSERTION_VERSION

Invalid SAML Response Assertion version. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_ISSUE_INSTANT

Invalid SAML Response Issue. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_STATUS

Invalid SAML Response Status. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_STATUS_REQUESTER_URI

Invalid SAML Response Status Requester URI. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_STATUS_RESPONDER_URI

Invalid SAML Response Status Response URI. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_STATUS_VERSION_MISMATCH_URL

Invalid SAML Response Status Version Mismatch URI. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE

Invalid SAML Response. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_DESTINATION

Invalid SAML Response Destination. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_VERSION_OR_ASSERTION_VERSION

Invalid SAML Response Version or Assertion Version. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_ASSERTION_SUBJECT

Invalid SAML Response Assertion Subject. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_ASSERTION_SUBJECT_NAMEID

Invalid SAML Response Assertion Subject NameId. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_ASSERTION_ISSUER

Invalid SAML Response Assertion Issuer. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_ASSERTION_CONDITION_AUDIENCE

Invalid SAML Response Assertion Condition Audience. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_ASSERTION_AUTHNSTATEMENT

Invalid SAML Response Assertion AuthNStatement. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_ASSERTION_ATTRIBUTE

Invalid SAML Response Assertion Attribute. Please contact cymmetri administrator.

MULTIPLE_ASSERTIONS_IN_RESPONSE_NOT_SUPPORTED

Multiple Assertion in Response Not Supported. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_ASSERTION_SIGNATURE

Invalid SAML Response Assertion Signature. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_SIGNATURE

Invalid SAML Response Signature. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_ASSERTION_CONDITION

Invalid SAML Response Assertion Condition. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_ASSERTION

Invalid SAML Response Assertion. Please contact cymmetri administrator.

INVALID_SAML_RESPONSE_ISSUER

Invalid SAML Response Issuer. Please contact cymmetri administrator.

IDP_CONFIGURATION_NOT_FOUND

Idp Configuration Not Found. Please contact cymmetri administrator.

SP_ID_IDP_ID_LOGIN_EMPTY

Service provider or identity provider login not provided. Please contact cymmetri administrator.

SERVICE_PROVIDER_CONFIGURATION_NOT_FOUND

Service Provider Configuration Not Found. Please contact cymmetri administrator.

ERROR_BUILDING_SAML_AUTHN_REQUEST

Failed To Build SAML Authentication Request. Please contact cymmetri administrator.

ERROR_PERSISTING_SAML_AUTHN_REQUEST

Failed To Persist SAML Authentication Request. Please contact cymmetri administrator.

ERROR_SENDING_SAML_AUTHN_REQUEST

Failed to Send SAML Authentication Request. Please contact cymmetri administrator.

USER_EMAIL_ADDRESS_NOT_PRESENT

User Email Not Found. Please contact cymmetri administrator.

USER_LOGIN_NOT_PRESENT

User Login Not Found. Please contact cymmetri administrator.

EMAIL_ADDRESS_DOES_NOT_MATCH

Email Address does not matching. Please contact cymmetri administrator.

LOGIN_DOES_NOT_MATCH

Login does not match. Please contact cymmetri administrator.

USER_NOT_AVAILABLE

User is not present. Please contact cymmetri administrator.

SERVICE_PROVIDER_NOT_FOUND

Service provider is not found. Please contact cymmetri administrator.

UNAUTHORIZED_ACCESS

Unauthorized Access. Please contact cymmetri administrator.

UNAUTHORIZED

Unauthorized Access. Please contact cymmetri administrator.

USER_NOT_FOUND

User Not found. Please contact cymmetri administrator.

DATA_NOT_PRESENT

Application configuration does not exist. Please contact cymmetri administrator.

ARGUMENT_IS_REQUIRED

Please correct Input and try again. Please contact cymmetri administrator.

APPLICATION_CONFIG_EXISTS

Application Configuration already exists. Please contact cymmetri administrator.

APPLICATION_CONFIG_NOT_PRESENT

Application configuration does not exists. Please contact cymmetri administrator.

INVALID_TOKEN

Invalid token Please contact cymmetri administrator.

TENANT_NOT_FOUND

Tenant detail not availaible. Please contact cymmetri administrator.

INVALID_APPLICATION_ID

Invalid application id. Please contact cymmetri administrator.

APPLICATION_WITH_ISSUER_NOT_FOUND

Application configuration with issuer not found. Please contact cymmetri administrator.

EXCEPTION_OCCURED_WITH_TENANT_JKS

Please contact cymmetri administrator.

EXCEPTION_OCCURED_WITH_TENANT_JKS_KEY_GENERATE

Please contact cymmetri administrator.

APPLICATION_NOT_ASSIGNED_TO_USER

Application is not assigned to the user. Please contact cymmetri administrator.

USER_NOT_ASSIGNED_SERVICE_PROVIDER_ERROR

User is not assigned to the service provider. Please contact cymmetri administrator.

SOMETHING_WENT_WRONG

Please contact cymmetri administrator.

SERVICE_PROVIDER_NAMEIDVALUE_MISMATCH_ERROR

Service provider nameId value does not match with configured application. Please contact cymmetri administrator.

SERVICE_PROVIDER_NAMEID_MISMATCH_ERROR

Service provider nameId value does not match with configured application. Please contact cymmetri administrator.

TENANT_HOST_NOT_FOUND

Please contact cymmetri administrator.

APPLICATION_CONFIG_NOT_FOUND

Application Configuration not found. Please contact cymmetri administrator.

SAMLREQUEST_NOT_PRESENT_IN_REQUEST

SAML Request is not present in Request. Please contact cymmetri administrator.

CONFIGURED_REQUEST_ISSUER_AND_SAML_REQUEST_NOT_ISSUER_NOT_MATCH

Application issuer Configuration does not match. Please contact cymmetri administrator.

INVALID_REQUEST_ISSUER

Invalid Request Issuer. Please contact cymmetri administrator.

IDENTITY_TOKEN_SAML_REQUEST_NOT_FOUND

Invalid Identity SAML Request Token. Please contact cymmetri administrator.

IDENTITY_REFRESH_SAML_REQUEST_NOT_FOUND

Invalid Refresh SAML Request Token. Please contact cymmetri administrator.

USER_NOT_ASSIGNED_TO_APPLICATION

User is not associated with the application. Please contact cymmetri administrator.

SSO_ERROR_SENDING_SAML_RESPONSE

Error Sending SAML Response. Please contact cymmetri administrator.

SSO_CONFIG_NOT_FOUND_APPLICATION_ID

SSO configuration not found for application. Please contact cymmetri administrator.

SSO_USER_NOT_FOUND

SSO user found for application. Please contact cymmetri administrator.

INTERNAL_SERVER_ERROR

Please contact cymmetri administrator.

IDP_SSO_JKS_MANAGER_FAILED

Please contact cymmetri administrator.

IDP_SSO_CUSTOM_JKS_FAILED

Please contact cymmetri administrator.

IDP_SSO_FAILED

SSO failed for identity provider. Please contact cymmetri administrator.

SERVICE_PROVIDER_SESSION_NOT_FOUND

Service provider session not availaible. Please contact cymmetri administrator.

INVALID_SP_INITIATED_REQUEST

Invalid service provider request. Please contact cymmetri administrator.

ERROR_PARSING_SAML_SLO

Error validating saml slo request. Please contact cymmetri administrator.

SERVICE_PROVIDER_ERROR

Failed with service provider. Please contact cymmetri administrator.

EXPIRED_REFRESH_TOKEN

Refresh token is expired. Please contact cymmetri administrator.

INVALID_REFRESH_TOKEN

Invalid refresh token. Please contact cymmetri administrator.

EMPTY_REFRESH_TOKEN

Empty refresh token. Please contact cymmetri administrator.

REFRESH_TOKEN_COOKIE_NOT_PRESENT

Refresh token cookie not present. Please contact cymmetri administrator.

APPLICATION_ID_NOT_PRESENT_IN_CONFIG

Application id not present. Please contact cymmetri administrator.

APPLICATION_ID_NOT_PRESENT_IN_REQUEST

Application id is not present in request Please contact cymmetri administrator.

EXPIRED_SSO_IDENTITY_TOKEN

SSO identity token is expired. Please contact cymmetri administrator.

EMPTY_SSO_IDENTITY_TOKEN

SSO identity token is invalid. Please contact cymmetri administrator.

REQUEST_ISSUER_FROM_SAML_REQUEST_NOT_PRESNETTITY_TOKEN

Request issuer is not present in saml request. Please contact cymmetri administrator.

INVALID_SSO_IDENTITY_TOKEN

Invalid SSO identity token. Please contact cymmetri administrator.

IDP_SLO_FAILED

Identity provider single logout failed. Please contact cymmetri administrator.

BUILD_SLO_REQUEST_FAILED

Build to failed single logout request. Please contact cymmetri administrator.

SLO_REQUEST_SEND_FAILED

Failed to send single logout request. Please contact cymmetri administrator.

SLO_RESPONSE_SEND_FAILED

Failed to send single logout response. Please contact cymmetri administrator.

ERROR_PERSISTING_SLO_REQUEST

Failed to persist single logout request. Please contact cymmetri administrator.

SLO_RESPONSE_SAML_ATTRIBUTE_VALIDATION_FAILED

Failed to validate single logout response attribute. Please contact cymmetri administrator.

INVALID_SAML_SLO_RESPONSE

Invalid saml single logout response. Please contact cymmetri administrator.

INVALID_SAML_SLO_MESSAGE

Invalid saml single logout message. Please contact cymmetri administrator.

SLO_REQUEST_VALIDATION_FAILED

Failed to validate single logout request. Please contact cymmetri administrator.

SLO_RESPONSE_VALIDATION_FAILED

Failed to validate single logout response. Please contact cymmetri administrator.

REMOVE_USER_BEFORE_APPLICATION

Users should get removed before removing the application.

PROVSRVC.REMOVE_USER_BEFORE_APPLICATION

Users should get removed before removing the application.

PAMSRVC.INVALID_ARGUMENTS

AD Parameter not found

PAMSRVC.IMPORT_DATA_TO_CSV_FILE_FAILED

CSV file not generated

PAMSRVC.UPDATE_AD_USER_PASSWORD_FAILED

Password update fail

PAMSRVC.VAULT_USER_ALREADY_AVAILABLE

Vault user already exist

PAMSRVC.BREAK_GLASS_NOT_FOUND

Break Glass Configuration Not Found

PAMSRVC.SERVER_ALREADY_EXISTS

Device Already Exists

DORMANCY_DISABLE_DAYS_EXCEEDED

Config days exceeded

PAMSRVC.DORMANCY_DISABLE_DAYS_EXCEEDED

Config days exceeded

SAMLSPSRVC.SOME_ERROR_OCCURRED_WORKING_ON_IT

Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_IDENTITY_PROVIDER_STATUS

Invalid Identity Provider Status. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_ARGUMENTS

Please correct Input and try again. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SERVICE_PROVIDER_STATUS

Invalid Service Provider Status. Please contact cymmetri administrator.

SAMLSPSRVC.MANDATORY_FIELD_EXCEPTION

Mandatory Field is Missing. Please contact cymmetri administrator.

SAMLSPSRVC.TENANT_OR_HOST_NOT_RECEIVED_FROM_NGINX

Please contact cymmetri administrator.

SAMLSPSRVC.TENANT_OR_HOST_PROTO_NOT_RECEIVED_FROM_NGINX

Please contact cymmetri administrator.

SAMLSPSRVC.SOME_IMPERSONATE_ACCESS

Unauthorized Access. Please contact cymmetri administrator.

SAMLSPSRVC.SERVICE_PROVIDER_INBOUND_MESSAGE_ERROR

Invalid SAML Message Received. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_ASSERTION_VERSION

Invalid SAML Response Assertion version. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_ISSUE_INSTANT

Invalid SAML Response Issue. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_STATUS

Invalid SAML Response Status. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_STATUS_REQUESTER_URI

Invalid SAML Response Status Requester URI. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_STATUS_RESPONDER_URI

Invalid SAML Response Status Response URI. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_STATUS_VERSION_MISMATCH_URL

Invalid SAML Response Status Version Mismatch URI. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE

Invalid SAML Response. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_DESTINATION

Invalid SAML Response Destination. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_VERSION_OR_ASSERTION_VERSION

Invalid SAML Response Version or Assertion Version. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_ASSERTION_SUBJECT

Invalid SAML Response Assertion Subject. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_ASSERTION_SUBJECT_NAMEID

Invalid SAML Response Assertion Subject NameId. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_ASSERTION_ISSUER

Invalid SAML Response Assertion Issuer. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_ASSERTION_CONDITION_AUDIENCE

Invalid SAML Response Assertion Condition Audience. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_ASSERTION_AUTHNSTATEMENT

Invalid SAML Response Assertion AuthNStatement. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_ASSERTION_ATTRIBUTE

Invalid SAML Response Assertion Attribute. Please contact cymmetri administrator.

SAMLSPSRVC.MULTIPLE_ASSERTIONS_IN_RESPONSE_NOT_SUPPORTED

Multiple Assertion in Response Not Supported. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_ASSERTION_SIGNATURE

Invalid SAML Response Assertion Signature. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_SIGNATURE

Invalid SAML Response Signature. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_ASSERTION_CONDITION

Invalid SAML Response Assertion Condition. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_ASSERTION

Invalid SAML Response Assertion. Please contact cymmetri administrator.

SAMLSPSRVC.INVALID_SAML_RESPONSE_ISSUER

Invalid SAML Response Issuer. Please contact cymmetri administrator.

SAMLSPSRVC.IDP_CONFIGURATION_NOT_FOUND

Idp Configuration Not Found. Please contact cymmetri administrator.

SAMLSPSRVC.SP_ID_IDP_ID_LOGIN_EMPTY

Service provider or identity provider login not provided. Please contact cymmetri administrator.

SAMLSPSRVC.SERVICE_PROVIDER_CONFIGURATION_NOT_FOUND

Service Provider Configuration Not Found. Please contact cymmetri administrator.

SAMLSPSRVC.ERROR_BUILDING_SAML_AUTHN_REQUEST

Failed To Build SAML Authentication Request. Please contact cymmetri administrator.

SAMLSPSRVC.ERROR_PERSISTING_SAML_AUTHN_REQUEST

Failed To Persist SAML Authentication Request. Please contact cymmetri administrator.

SAMLSPSRVC.ERROR_SENDING_SAML_AUTHN_REQUEST

Failed to Send SAML Authentication Request. Please contact cymmetri administrator.

SAMLSPSRVC.USER_EMAIL_ADDRESS_NOT_PRESENT

User Email Not Found. Please contact cymmetri administrator.

SAMLSPSRVC.USER_LOGIN_NOT_PRESENT

User Login Not Found. Please contact cymmetri administrator.

SAMLSPSRVC.EMAIL_ADDRESS_DOES_NOT_MATCH

Email Address does not matching. Please contact cymmetri administrator.

SAMLSPSRVC.LOGIN_DOES_NOT_MATCH

Login does not match. Please contact cymmetri administrator.

SAMLSPSRVC.USER_NOT_AVAILABLE

User is not present. Please contact cymmetri administrator.

SAMLSPSRVC.SERVICE_PROVIDER_NOT_FOUND

Service provider is not found. Please contact cymmetri administrator.

SAMLSPSRVC.UNAUTHORIZED_ACCESS

Unauthorized Access. Please contact cymmetri administrator.

SAMLSPSRVC.UNAUTHORIZED

Unauthorized Access. Please contact cymmetri administrator.

SAMLSPSRVC.USER_NOT_FOUND

User Not found. Please contact cymmetri administrator.

SAMLSRVC.SOME_ERROR_OCCURRED_WORKING_ON_IT

Please contact cymmetri administrator.

SAMLSRVC.DATA_NOT_PRESENT

Application configuration does not exist. Please contact cymmetri administrator.

SAMLSRVC.ARGUMENT_IS_REQUIRED

Please correct Input and try again. Please contact cymmetri administrator.

SAMLSRVC.APPLICATION_CONFIG_EXISTS

Application Configuration already exists. Please contact cymmetri administrator.

SAMLSRVC.APPLICATION_CONFIG_NOT_PRESENT

Application configuration does not exists. Please contact cymmetri administrator.

SAMLSRVC.INVALID_TOKEN

Invalid token Please contact cymmetri administrator.

SAMLSRVC.TENANT_NOT_FOUND

Tenant detail not availaible. Please contact cymmetri administrator.

SAMLSRVC.INVALID_APPLICATION_ID

Invalid application id. Please contact cymmetri administrator.

SAMLSRVC.APPLICATION_WITH_ISSUER_NOT_FOUND

Application configuration with issuer not found. Please contact cymmetri administrator.

SAMLSRVC.EXCEPTION_OCCURED_WITH_TENANT_JKS

Please contact cymmetri administrator.

SAMLSRVC.EXCEPTION_OCCURED_WITH_TENANT_JKS_KEY_GENERATE

Please contact cymmetri administrator.

SAMLSRVC.APPLICATION_NOT_ASSIGNED_TO_USER

Application is not assigned to the user. Please contact cymmetri administrator.

SAMLSRVC.TENANT_OR_HOST_PROTO_NOT_RECEIVED_FROM_NGINX

Please contact cymmetri administrator.

SAMLSRVC.USER_NOT_ASSIGNED_SERVICE_PROVIDER_ERROR

User is not assigned to the service provider. Please contact cymmetri administrator.

SAMLSRVC.SOMETHING_WENT_WRONG

Please contact cymmetri administrator.

SAMLSRVC.SERVICE_PROVIDER_NAMEIDVALUE_MISMATCH_ERROR

Service provider nameId value does not match with configured application. Please contact cymmetri administrator.

SAMLSRVC.SERVICE_PROVIDER_NAMEID_MISMATCH_ERROR

Service provider nameId value does not match with configured application. Please contact cymmetri administrator.

SAMLSRVC.TENANT_HOST_NOT_FOUND

Please contact cymmetri administrator.

SAMLSRVC.TENANT_OR_HOST_NOT_RECEIVED_FROM_NGINX

Please contact cymmetri administrator.

SAMLSRVC.APPLICATION_CONFIG_NOT_FOUND

Application Configuration not found. Please contact cymmetri administrator.

SAMLSRVC.SAMLREQUEST_NOT_PRESENT_IN_REQUEST

SAML Request is not present in Request. Please contact cymmetri administrator.

SAMLSRVC.CONFIGURED_REQUEST_ISSUER_AND_SAML_REQUEST_NOT_ISSUER_NOT_MATCH

Application issuer Configuration does not match. Please contact cymmetri administrator.

SAMLSRVC.INVALID_REQUEST_ISSUER

Invalid Request Issuer. Please contact cymmetri administrator.

SAMLSRVC.IDENTITY_TOKEN_SAML_REQUEST_NOT_FOUND

Invalid Identity SAML Request Token. Please contact cymmetri administrator.

SAMLSRVC.IDENTITY_REFRESH_SAML_REQUEST_NOT_FOUND

Invalid Refresh SAML Request Token. Please contact cymmetri administrator.

SAMLSRVC.USER_NOT_ASSIGNED_TO_APPLICATION

User is not associated with the application. Please contact cymmetri administrator.

SAMLSRVC.SSO_ERROR_SENDING_SAML_RESPONSE

Error Sending SAML Response. Please contact cymmetri administrator.

SAMLSRVC.SSO_CONFIG_NOT_FOUND_APPLICATION_ID

SSO configuration not found for application. Please contact cymmetri administrator.

SAMLSRVC.SSO_USER_NOT_FOUND

SSO user found for application. Please contact cymmetri administrator.

SAMLSRVC.INTERNAL_SERVER_ERROR

Please contact cymmetri administrator.

SAMLSRVC.IDP_SSO_JKS_MANAGER_FAILED

Please contact cymmetri administrator.

SAMLSRVC.IDP_SSO_CUSTOM_JKS_FAILED

Please contact cymmetri administrator.

SAMLSRVC.IDP_SSO_FAILED

SSO failed for identity provider. Please contact cymmetri administrator.

SAMLSRVC.SERVICE_PROVIDER_SESSION_NOT_FOUND

Service provider session not availaible. Please contact cymmetri administrator.

SAMLSRVC.INVALID_ARGUMENTS

Please correct input and try again. Please contact cymmetri administrator.

SAMLSRVC.INVALID_SP_INITIATED_REQUEST

Invalid service provider request. Please contact cymmetri administrator.

SAMLSRVC.ERROR_PARSING_SAML_SLO

Error validating saml slo request. Please contact cymmetri administrator.

SAMLSRVC.SERVICE_PROVIDER_ERROR

Failed with service provider. Please contact cymmetri administrator.

SAMLSRVC.EXPIRED_REFRESH_TOKEN

Refresh token is expired. Please contact cymmetri administrator.

SAMLSRVC.INVALID_REFRESH_TOKEN

Invalid refresh token. Please contact cymmetri administrator.

SAMLSRVC.EMPTY_REFRESH_TOKEN

Empty refresh token. Please contact cymmetri administrator.

SAMLSRVC.REFRESH_TOKEN_COOKIE_NOT_PRESENT

Refresh token cookie not present. Please contact cymmetri administrator.

SAMLSRVC.APPLICATION_ID_NOT_PRESENT_IN_CONFIG

Application id not present. Please contact cymmetri administrator.

SAMLSRVC.APPLICATION_ID_NOT_PRESENT_IN_REQUEST

Application id is not present in request Please contact cymmetri administrator.

SAMLSRVC.EXPIRED_SSO_IDENTITY_TOKEN

SSO identity token is expired. Please contact cymmetri administrator.

SAMLSRVC.EMPTY_SSO_IDENTITY_TOKEN

SSO identity token is invalid. Please contact cymmetri administrator.

SAMLSRVC.REQUEST_ISSUER_FROM_SAML_REQUEST_NOT_PRESNETTITY_TOKEN

Request issuer is not present in saml request. Please contact cymmetri administrator.

SAMLSRVC.INVALID_SSO_IDENTITY_TOKEN

Invalid SSO identity token. Please contact cymmetri administrator.

SAMLSRVC.IDP_SLO_FAILED

Identity provider single logout failed. Please contact cymmetri administrator.

SAMLSRVC.BUILD_SLO_REQUEST_FAILED

Build to failed single logout request. Please contact cymmetri administrator.

SAMLSRVC.SLO_REQUEST_SEND_FAILED

Failed to send single logout request. Please contact cymmetri administrator.

SAMLSRVC.SLO_RESPONSE_SEND_FAILED

Failed to send single logout response. Please contact cymmetri administrator.

SAMLSRVC.ERROR_PERSISTING_SLO_REQUEST

Failed to persist single logout request. Please contact cymmetri administrator.

SAMLSRVC.SLO_RESPONSE_SAML_ATTRIBUTE_VALIDATION_FAILED

Failed to validate single logout response attribute. Please contact cymmetri administrator.

SAMLSRVC.INVALID_SAML_SLO_RESPONSE

Invalid saml single logout response. Please contact cymmetri administrator.

SAMLSRVC.INVALID_SAML_SLO_MESSAGE

Invalid saml single logout message. Please contact cymmetri administrator.

SAMLSRVC.SLO_REQUEST_VALIDATION_FAILED

Failed to validate single logout request. Please contact cymmetri administrator.

SAMLSRVC.SLO_RESPONSE_VALIDATION_FAILED

Failed to validate single logout response. Please contact cymmetri administrator.

SAMLSRVC.UNAUTHORIZED

Unauthorized. Please contact cymmetri administrator.

INVALID_USER_SESSION

User login session is invalid

USER_NOT_CONFIGURED_FOR_EXTERNAL_LOGOUT

User is not configured for external identity provider logout

USER_DOES_NOT_HAVE_ANY_ACTIVE_SSO_SESSION

User does not have any active sso login session

ISSUE_INSTANT_EXCEPTION

Invalid user issue instant exception

NOT_ON_OR_AFTER_EXCEPTION

Saml attribute is not valid before and after timestamp

NAME_ID_FORMAT_EXCEPTION

Invalid user name id is not valid

SESSION_INDEX_EXCEPTION

User login session index is invalid

DESTINATION_EXCEPTION

Saml attribute destination is invalid

IDENTITY_PROVIDER_EXCEPTION

External identity provider is invalid

IN_RESPONSE_TO

Saml attribute in response attribute is invalid

ISSUER_EXCEPTION

Saml attribute issuer is invalid

DATALOGGER.ALREADY_ACTIVATED

Already activated

DATALOGGER.ALREADY_DEACTIVATED

Already deactivated

DATALOGGER.SYSLOG_CONFIG_TEST_FAILED

Syslog configuration test failed

DATALOGGER.SYSLOG_CONFIG_NOT_FOUND

Syslog configuration not found

PAM_CONFIG_DATA_NOT_FOUND

Pam Configuration data not found

PAM_INVALID_CONFIG

Invalid Pam Configuration found

PAMSRVC.INTERNAL_ERROR

Invalid password. Please try again

PAMSRVC.PAM_CONNECTION_FAIL

Connection Fail

PAMSRVC.CONNECTION_FAILED

Connection Fail

REPORT.INVALID_ARGUMENTS

Please correct the input and try again

PROVSRVC.PASSWORDFILTER_AND_APPLICATION_DOES_NOT_SAME

Filtered application and included/excluded cannot be the same

PROVSRVC.PASSWORDFILTER_ALREADY_CONFIGURED

Application is already configured for password filter

dagsrvc.INVALID_ARGUMENTS

Invalid argument.

dagsrvc.INVALID_ARGUMENTS

Invalid argument.

dagsrvc.SERVER_NAME_ALREADY_EXIST_EXCEPTION

Server name already exit.

dagsrvc.ROOT_LOCATION_NOT_FOUND

Server details not found.

DAGSRVC.DAG_SHARED_SERVER_ALREADY_EXISTS

Server Configuration already exist

DAGSRVC.DAG_SHARED_SERVER_NOT_FOUND

One or more shared servers not found

PROVSRVC.APPLICATION_ROLE_NOT_FOUND

Application Role not found

PORTAL.EXPIRY_DATA_NOT_FOUND

Expiry data not found

PORTAL.EXPIRED_LINK

Link has been expired

REGSRVC.ACCOUNT_NOT_ACTIVE

Tenant account inactive. Please contact support

USRSRVC.IMPORT_SCHEMA_NOT_FOUND

Import template not found

SLFSRVC.OPERATION_NOT_ACTIVE

Operation not configured

WKFLSRVC.WORKFLOW_PREFERENCE_CONFIG_NOT_FOUND

Workflow Preference Config not found

USRSRVC.GROUP_ALREADY_ASSIGN_TO_USER

Group Already Assigned to User.

USRSRVC.USER_INACTIVE_CONFIG_NOT_FOUND

Inactive User Config not found

UTILSRVC.TEAMS_CONFIG_ALREADY_EXIST

Teams Config already exist

UTILSRVC.TEAMS_CONFIG_NOT_FOUND

Teams Config Not Found

PAMSRVC.RULE_CONFIGURE_ALREADY_EXIST

Configuration already exists

PAMSRVC.EMPTY_CONDITION_EXCEPTION

Empty Condition exception

SLFSRVC.INVALID_MANAGER_EXCEPTION

Invalid Manager

SLFSRVC.INVALID_MANAGER

Invalid Manager

SLFSRVC.USER_NOT_FOUND

User not found. Please try again.

WKFLSRVC.SELF_APPROVAL_CONFIG_EXIST

Self Approval config already exists

WKFLSRVC.SELF_APPROVAL_CONFIG_NOT_FOUND

Self Approval config not found

MFASRVC.RESEND_PERIOD_NOT_ALLOWED

Please wait we are enabling resend operation

MFASRVC.RESEND_TIME_EXCEED

Allowed resend attempt exceed please try after some time

ANALYTICS.INVALID_LOG_ARGUMENTS

Invalid arguments

ANALYTICS.UNAUTHORIZED

Unauthorized. Please contact cymmetri administrator.

ANALYTICS.ALREADY_ACTIVATED

Already activated

ANALYTICS.ALREADY_DEACTIVATED

Already deactivated

DATALOGGER.ALREADY_EXISTS

Already exists

DATALOGGER.CONNECTION_FAILED

Connection Fail

DATALOGGER.FORBIDDEN

Please contact system administrator.

DATALOGGER.INVALID_ARGUMENTS

Invalid arguments

DATALOGGER.SYNC_NOT_SUPPORTED

Sync not supported

ANALYTICS.SYSLOG_CONFIG_NOT_FOUND

Syslog configuration not found

ANALYTICS.SYSLOG_CONFIG_TEST_FAILED

Syslog configuration test failed

DATALOGGER.UNAUTHORIZED

Unauthorized. Please contact cymmetri administrator.

REPORT.ALREADY_ACTIVATED

Already activated

REPORT.ALREADY_DEACTIVATED

Already deactivated

REPORT.ALREADY_EXISTS

Already exists

ANALYTICS.CONNECTION_FAILED

Failed to send report.

REPORT.CONTENT_NOT_FOUND

Content not found

REPORT.EMAIL_EXISTS

Email already exists

ANALYTICS.EMAIL_NOT_EXISTS_EXCEPTION

User Email Not Found. Please contact cymmetri administrator.

REPORT.FORBIDDEN

Please contact system administrator.

ANALYTICS.INVALID_ARGUMENTS

Please correct the input and try again

REPORT.INVALID_CRON_EXPRESSION

Invalid cron expression

REPORT.INVALID_FREQUENCY_CONFIG

Invalid frequency config

REPORT.INVALID_REPORT_CONFIG

Invalid report config

REPORT.INVALID_SCHEDULER_TASK_EXECUTION_ID

Invalid schedular task execution ID

REPORT.REPORT_BATCH_TASK_NOT_FOUND

Batch task not found

REPORT.REPORT_EXISTS_EXCEPTION

Report already exists

REPORT.REPORT_NOT_FOUND

Report not found

REPORT.SEND_EMAIL_FAILED_EXCEPTION

Email Sending failed

REPORT.UNAUTHORIZED

Please contact cymmetri administrator.

RISKENGINE.ALREADY_ACTIVATED

Already activated

RISKENGINE.ALREADY_DEACTIVATED

Already deactivated

RISKENGINE.ALREADY_EXISTS

Already exists

RISKENGINE.CONNECTION_FAILED

Connection Fail

RISKENGINE.CONNECTOR_NOT_AVAILABLE

Connector not available

RISKENGINE.FORBIDDEN

Please contact cymmetri administrator.

RISKENGINE.INVALID_ARGUMENTS

Invalid arguments

RISKENGINE.INVALID_RISK_SYNC_TASK_STATUS

Invalid risk sync task status

RISKENGINE.NO_MAPPING_FOUND

No mapping found

RISKENGINE.RISK_CONFIG_NOT_FOUND

Risk config not found

RISKENGINE.RISK_NOT_FOUND

Risk not found

RISKENGINE.RISK_SYNC_TASK_IN_PROGRESS

Risk sync task in progress

RISKENGINE.RISK_SYNC_TASK_NOT_IN_PROGRESS

Risk sync task not in progress

RISKENGINE.UNAUTHORIZED

Please contact cymmetri administrator.

RISKENGINE.UNSUPPORTED_FIELD

Field not supported

RISKENGINE.UNKNOWN

Please contact cymmetri administrator.

here
https://help.cymmetri.io

Android

NA

iOS

NA

Mac OS

NA

Windows

Tenant Branding

Tenant branding in Cymmetri allows you to personalize and enhance the visual identity of your environment. With tenant branding, you can customize the appearance of your platform, including logos, color schemes, and even tailored messages, aligning it with your organization's branding guidelines.

This not only creates a cohesive and professional user experience but also reinforces your brand's presence throughout the Cymmetri environment. It's a powerful tool for organizations looking to maintain a consistent and recognizable image while utilizing Cymmetri's identity and management capabilities.

The Cymmetri platform allows a certain level of customization to your tenant from the administration panel. This includes the ability to modify the default Cymmetri branding scheme to your own Organization’s branding scheme.

  1. Your Organization Name and Tagline

  2. Your Organization Logo

  3. Your Organization Branding Colors (Primary, Secondary, Accent Colors)

Configuring your tenant branding

  1. To access the branding menu, first click on the Configuration menu on the left-hand side and then proceed by clicking on the Branding menu item.

  2. Start the configuration by entering your Organization Name and Tag Line

  3. Proceed by adding a Welcome text and Welcome Tagline and select whether the Cymmetri help icon should be visible to the user or not

  4. Proceed by adding your URL to the Website text box and click “Fetch Brand”.

  5. If your organization’s branding is available, the logo and the corresponding color scheme will be displayed in the menu below.

  6. If your branding is unavailable, you may configure it yourself by uploading your logo and editing your primary color, secondary color, and accent color.

  7. Click on the Save and Sync Server button to make the branding configuration apply to the entire website.

The configuration will be applied in a few seconds to reflect your branding.

In Cymmetri, the administrator now has the option to select the "Reset to default theme" button, allowing them to revert to the original theme.

Personalize Notification Templates

Notifications are triggered from the Cymmetri platform for various actions occurring on the platform either through direct action by the end-user or by the virtue of some backend action (such as running of a scheduler for a campaign). Cymmetri platform ships with default notification templates listed below-

  1. Mandatory Notifications

  • Sign-up / Registration

  • OTP Notification

  • Access Code Manager Notification

  • Access Code User Notification

  1. Optional Notifications

  • Workflow Notification

  • Reviewer Notification

  • Application Access Approval Request

  • Application Assignment

  • Delegation Assignee Notification

  • User Activation

  • Application Scheduled Deprovisioning

  • Delegation User Notification

  • Application Access Approval Request Denied by Approver

  • Application Access Approval Request Granted

  • User Notification

  • Login Failed

  • Password Expiry Notification

  • Review Assignment Notification

  • Self Approval Notification

  • Login Adaptive Failed Notification

  • MFA Failed Notification

  • User Threshold

  • User attribute update / Profile update

  • Pending Access Certification Notification

  • Ad-Hoc Certification Notification

  • User Risk score changes

Please note: The above notifications are available out of the box. The system also allows custom notifications to be triggered for specific events using the Cymmetri Webhooks. The custom action trigger can call an existing Cymmetri notification template or a custom template can be included in the webhook code.

The default templates may be modified by the administrator using the following process:

  1. Access the notification templates menu by clicking on the configuration menu on the left-hand side menu bar and then clicking on the Notification templates pop-up menu.

  2. Click on the eye icon to preview the corresponding template

  1. Values in <> anchor tags and ${} reflect macros.

  2. Click on the pencil icon shown above the image to edit the template.

  3. We may treat this template as an email, and edit the subject of the mail.

    By default, the email notification will be sent to the corresponding affected end-user, but selecting the toggle option for “Send notification to Reporting Manager” will also copy the mail to the Reporting manager of the affected end-user, allowing for offline follow-up for the notification.

  4. The administrator may edit the HTML using the provided HTML editor to add/change any template button/text/background. The macros required for the particular template are already provided in the sample default notification template.

  5. Click on the Save button to save the notification template.

3.0.x Consolidated

(3.0.1 - 3.0.12)

Edit Users

The Edit User functionality allows administrators to modify user details within the Identity Hub.

Steps to Edit a User:

  • Navigate to Identity Hub -> Users, select the specific user you wish to edit, then go to the User Info page and click on Edit User

  • The Edit User form will be displayed, where you can modify the user's information as needed.

  • After making the necessary changes, click Save to update the user's details.

  • Saving the changes may also trigger updates in target applications, depending on the configuration. This ensures that any modifications done are synchronized across all relevant systems.

Custom Attributes

Custom Attributes may be added for all user entities in your Cymmetri Platform. This allows organizations to add custom user attributes, that are used across the applications in the organization.

For example, your organization has a custom attribute that captures and uses the local language of your employees and vendors to provide local services. This attribute may be stored in your Active Directory and may need to be synchronized to your organization’s other applications during the course of an employee or vendor’s employment.

Cymmetri platform allows the administrator to define custom attributes on a tenant-wide level.

Custom attributes can be used at various places like when creating a user, as a filter when searching for users, and are visible in the others section of user info

Configuring Custom Attributes

  1. To start configuring custom attributes, click on the Configurations menu on the left-hand side and then click on the Custom Attributes menu.

  1. Click on the Add New button to start adding a custom attribute

  2. Fields to be updated:

    1. Name/ Key: refers to the label assigned to the custom attribute.

    2. Description: allows you to provide additional details or notes about the custom attribute for reference and clarity.

    3. Status: Allows to activate the custom attribute. Only if it is set to active, is the attribute available to use in the User Object.

    Note: A custom attribute once created can only be set to inactive, it cannot be deleted.

Importing Users

Users may be imported into the Cymmetri platform using the bulk Import Users feature.

Importing Users

For Importing Users in the Cymmetri platform administrator needs to click on Identity Hub > User menu and then click on the Bulk Import > Import Users button.

A screen pops up that lets you select the CSV file you want to upload to import the users, Upload the CSV file, you may also use the sample data file available and modify it to match your user details.

Click on the Upload File button and select the file you wish to import

Once the file is selected ensure that the default parameters selected match your requirements else you may change these parameters as per your requirement and click on the Next button.

Match the Column names from the CSV file with the Cymmetri User Attributes using this File Info dialog box.

Scroll down and click on the Import button. Note: A "Skip user workflow" check box is available to skip execution of any user workflow configured for the creation of users, if not selected it may trigger user creation workflow, and the process of importing users may slow down due to the numerous approvals that the approver might have to do.

Once Imported results of successfully Imported Users, Duplicate Users, or any error that occurred during import can be seen in Logs > Import History page

Admins

Cymmetri platform has six different admin roles with various levels of access to the various menus and resources on the administration portal of Cymmetri.

In addition to these six admin roles, Cymmetri also supports three different privileged user roles that grant varying levels of access (read, write, report) to privileged users within Cymmetri.

Administrators

The various admin roles on the Cymmetri Identity Platform may be described as follows:

Organization Administrator

This is the so-called 'super admin' administrator role in the Cymmetri platform. Administrators with this role have the authorization to modify any settings or make changes to the tenant.

Domain Administrator

This is a slightly less privileged administrator. Most tenant-wide system settings, such as the configuration of SMS and email providers (when configured by the tenant), are restricted for domain administrators. All other configurations can be viewed and edited by administrators with the Domain Administrator role.

Application Administrator

An administrator with the role of Application Administrator has access to Identity Hub configurations, including Application, User, and Group configurations. The Application Administrator can map users and groups to applications and can edit all configurations related to Application Management.

Report Administrator

An administrator with the role of Report Administrator has access to the Reports menu, which includes the ability to view, modify, and add new reports.

Help Desk Administrator

The Helpdesk administrator has access to a very limited set of administrative functionalities, such as, resetting password of the end-user, removing configured Multifactor authentication options, and other such common use-case

Read Only Administrator

All administrative users have editing access to the various administrative sections of the Cymmetri platform. However, administrators with the "Read Only Administrator" role do not have editing access to any of the settings or configurations; they only have "Read Only" access to the administrative section.

PAM Write Access

PAM Write Access in Cymmetri grants users the privilege to connect to servers via RDP or SSH and perform write or modification actions on those servers. Users with PAM Write Access have the ability to make changes, update configurations, and perform tasks that involve altering data or settings on the connected servers. This access level is typically assigned to administrators and IT personnel responsible for making configuration changes or updates on various servers within the Cymmetri environment.

PAM Read Access

PAM Read Access provides users with the ability to connect to servers using RDP or SSH and view the content and configurations on those servers. However, users with PAM Read Access do not have the authority to make modifications or changes to the server settings or data. This level of access is suitable for individuals who need to monitor server activities, check logs, or retrieve information from servers without the need to alter any server configurations.

PAM Report Access

PAM Report Access is designed for users who require access to PAM-related reports without the need to connect to servers via RDP or SSH directly. Users with PAM Report Access can generate and access reports that provide insights into server activities, access logs, or other relevant data within the Cymmetri. Such users can also configure schedulers to send timely reports to various other users. This level of access is beneficial for auditors, compliance teams, or individuals focused on analyzing server-related information for reporting and auditing purposes.

Adding a New Admin

Follow the steps mentioned below to promote a user as an admin in the Cymmetri platform.

Click on the Configuration menu on the right-hand side

Now click on the Admins sub-menu within the Configuration menu

Click on the "+Add New" button to add a new administrator

To assign an administrator role to a user, search for the user and then click the 'Assign' button.

Select the chosen administration role and click on Save

The administrator has been assigned the role of “Report Administrator”.

All Admins

All admins is a section where various Cymmetri admins listing is displayed to the admin user

Create Groups

Administrator tasks pertaining to bulk users may be eased by creating groups of users.

Creating User Groups

Access the group configuration page by clicking the Identity Hub >Groups menu on the left-hand side.

Click on the “+Add New” button to start creating a new group

Group Name: Indicates the name of the group.

Group Type: For environments not using Active Directory, either Local or Remote Group may be chosen, in case Active Directory is being used for synchronization in the tenant, the appropriate type according to the group policy object must be chosen.

Parent Group: If a parent group is chosen, all the policies and rules applicable to the parent group will be assigned to this new group, in addition to the policies and rules specifically applied to this new group.

Group Description: Optionally, a description may be provided to the group.

Once all the details have been entered click on the Save button and a new group is created.

Masters in Cymmetri

Masters are key-value pairs that can be defined for the entire tenant. The key(name) in this context refers to the label to be shown on the Cymmetri User Interface, and the value is the backend identifier used to reference this field in various processes, rules, and policies defined in the Cymmetri platform.

Cymmetri platform allows for configuring several masters in the system, the major classification among which are Global masters (which allow for creating master key-value pairs that may be used for various situations, such as creating a new department, designation, and other custom attributes for users in the system) and Zone masters (which are network configurations that may be used to whitelist or blacklist user access onto the platform as well as act as a source for adaptive Multi-factor authentication).

Global Masters

These are system-wide key-value pairs primarily used to setup key-value pairs referring to various masters as given below:

Types of Global Masters:

Adding a new Master

Follow the steps below to Add a New Master:

Click on the "+Add New" button to add a new master of any category mentioned above.

Enter the Name and Value for the new Master, then select the type of master you wish to create and enable the active toggle button to make the master active. Once all values are entered click on the Save button

A new Global Master is successfully created in the selected category

RBAC Master

The RBAC Master allows the maintenance of role entitlements for the organization.

Zone Masters

Zone masters indicate the network zones that may be used for blacklisting or whitelisting access to the Cymmetri Identity platform deployment. It may also be used for detecting users from certain zones and assigning relevant multi-factor authentication policies.

Zone Name: Used to refer to a zone in other configurations on the Cymmetri platform.

Inactive/Active: Toggle button to check whether the zone is active (configurable as a condition for other rules on the Cymmetri platform.)

Gateway IP: Refers to the Gateway IP address for the network zone.

Proxy IPs: Proxy Server IP addresses that may be used to be directed to this network or the IP addresses outside of the zone that would indicate a connection from this zone.

For adding a new Zone Master or for editing an existing one, Fill in all the mandatory details on the screen as shown above, click on the enable toggle button and finally click the “Save” button.

User Management

The User Management interface in Cymmetri provides an intuitive and efficient way to manage the users within Cymmetri. The interface is designed to support both list and card views, allowing administrators to easily navigate through user profiles according to their preferences.To access the User Management page, navigate through: Identity Hub -> User

Features

The UserManagement Page provides various features which eases the user management.

  • View Modes: Users can toggle between a list and a card view, providing flexibility in how information is displayed.

  • Search Functionality: Quickly find users with the integrated search feature, saving time and improving manageability.

  • Advanced Filtering: The granular filtering capability ensures that administrators can pinpoint users based on specific criteria, making user management tasks more streamlined. List of users can be narrowed down the using various filters, including:

    • Account Status

    • User Status

    • Users' Login Status

    • Location

    • Department

    • Designation

    • Usertype

    • Custom Attributes

User Information Display

For each user, the following information is prominently displayed:

  • Display Name: The full name of the user as it appears in the organization.

  • Email: The user's primary email address.

  • Mobile Number: Contact number of the user.

  • User Status Indicator: An intuitive green or red dot next to the display picture indicates whether a user is active or inactive, respectively.

Contextual Actions

A context menu associated with each user profile offers a suite of actions, enabling administrators to manage user accounts directly from the interface. Available actions include:

  • Reset Password: Securely reset a user's password.

  • Mark Inactive: Change a user's status to inactive.

  • Assign Group: Add the user to specific groups for access control and organizational purposes.

  • Assign Application: Allocate applications to the user as per their role and requirements.

  • Edit Info: Update user information such as email, mobile number, and other personal details.

  • Delete User: Remove the user from the system entirely.

Create Users

While users may be imported and synchronized from other Identity providers, sometimes users may need to be added manually by the administrator.

Steps to Create Users:

  1. First navigate to the User configuration page, by clicking on the Identity Hub > User menu on the left-hand side panel.

  2. Click on the “+Add New” button.

  3. Enter the required information and scroll down to add further information.

  4. Click on the Save button to move to the next configuration page, and copy the automatically generated password.

  5. Optionally a group can be assigned to the user.

  6. And also applications can be assigned to the user.

Once all the above steps are completed successfully the user is created with the assigned groups and assigned applications.

Global Search

Global Search is a powerful, word-based search feature that empowers users to instantly navigate across various pages in Cymmetri by simply typing in relevant keywords. This functionality streamlines the process of locating specific information, making it significantly easier to access any content within Cymmetri with just a few keystrokes. By incorporating Global Search in Cymmetri the time spent browsing through menus or sifting through irrelevant data is minimized, directly enhancing the productivity and user experience.

The Global Search feature is available in the top bar which makes it available on all pages as shown below:

For using the Global Search the user needs to click on the search box. When clicked it opens a search dialog box.

Note: The search dialog box can also be opened using Ctrl+K (in Windows) or Command+K (in Mac)

Upon entering a term, you'll receive precise matches or helpful suggestions. Simply browse the list and select the desired page to view it, clicking anywhere outside the search modal instantly closes it, allowing you to seamlessly return to your previous page.

The page also provides certain shortcuts which can be used for ease:

Esc: Close the search Dialog box

↓↑: for Navigate up and down the search list

Enter: For opening the selected page

The Search box appears below in non-administrative logins:

User Detail

This page is designed to provide a comprehensive view of an individual user's information, facilitating easy access and management for administrators.

User Profile Overview

The top section of the User Details Page showcases the following crucial user information:

Profile Picture

The user's profile picture is prominently displayed, offering a visual identification of the user. This feature aids in personalizing the user experience and making navigation more intuitive.

User's Status

Right next to the profile picture, users can find the current status of the user, which indicates whether the user is Active, Inactive, or Pending. This status helps in quickly understanding the user's engagement level.

Login ID

This is a unique identifier for the user within the system. It serves as a key piece of information for various administrative processes, including user tracking, support, and security checks.

Email ID

The user's Email ID is displayed, providing an essential communication link. It is used for sending notifications, password resets, and other critical communications.

Mobile Number

The user's mobile number is listed if provided. This number can be utilized for two-factor authentication, urgent alerts, or direct contact purposes.

This structured format ensures that an administrator or any authorized viewer can quickly access and understand a user's essential information without navigating through multiple pages.

Risk Details

The user's risk details are visible on the page to notify that the user is a high-risk user. On further clicking on that page it shows User's Risk metrics.

User Info Page

This page provides a comprehensive overview of the user information managed within our system. The data is categorized into several sections to facilitate easy access and understanding of each user's profile. These sections are detailed below.

Basic Information

  • First Name: The user's given name.

  • Middle Name: The user's middle name, if applicable.

  • Last Name: The user's family name.

  • Grade: The user's grade (a set of values needs to be defined for this field in Masters).

  • Designation: The specific title or position the user holds.

  • Date of Birth: The user's birth date.

  • Age: The user's current age, is calculated from the date of birth.

  • User Type: Classification of the user based on the user types defined in the system.

  • Login ID: The unique identifier used by the user to access the system.

Contact Information

  • Country: The country where the user is located.

  • City: The city within the country.

  • Mobile: The user's mobile phone number.

  • Email: The user's email address, is used for electronic correspondence.

  • Landline: The user's landline phone number, if applicable.

  • Address: The user's full postal address.

Organization Information

  • Employee ID: A unique identifier assigned to the user within the organization.

  • Department: The department to which the user is assigned.

  • Start Date: The date when the user commenced their current position.

  • End Date: If applicable, the date when the user's current position will or has ended.

  • Manager: The user's direct supervisor or manager.

Custom Attributes

Additionally, this page may display values for custom attributes specific to our organization. These attributes allow for the capture of information not covered by the standard categories but deemed necessary for our operations.

This comprehensive user information page ensures that all pertinent data regarding an individual within our organization is readily accessible, facilitating smooth operations, management decisions, and communication.

Applications Page

This page is designed to streamline the management and assignment process of applications for users. It offers a section where you can easily view all your assigned applications along with their current status. Additionally, it allows for the straightforward assignment of new applications to your profile.

  • Viewing Assigned Applications: Upon accessing the page, you will be presented with a list of applications currently assigned to you. Each application tile gives a snapshot of the application's status, enabling you to quickly assess which applications require your attention.

  • Assigning Roles: Application Roles can be assigned to the user, using the Assign Role option. This option also allows the assignment of multiple roles to a user.

  • Unassign Assigned Applications: Assigned applications can be removed using the delete option in the (⋮) menu.

  • Assigning New Applications: Should you need to add more applications to your list, the process is simple. Just click on the Add New Button located on the interface. This action opens up a selection window where you can choose additional applications that you wish to assign to the user.

  • Searching for Applications: To facilitate ease of access, a search function is incorporated into the interface. This feature allows you to quickly find specific applications by typing the name or part of it into the search bar, saving you time and effort from manually scrolling through the list of applications.

Note: In instances where an application has not been successfully assigned, the interface provides direct actions to resolve the issue without needing to navigate away from the page. Each application tile includes an (⋮) menu with two options:

  • Retry: If an application's assignment process encounters an issue, you can select this option to attempt assigning the application again.

  • Delete: If the assignment issue remains unresolved or if you no longer wish to keep the application, you can choose to remove the application from your list entirely.

Groups Page

This page provides an overview of the groups to which a user is assigned, reflecting the current status of each.

Viewing Assigned Groups and Their Status

Upon accessing the page, users are presented with a list of all the groups to which they are currently assigned. Each entry includes the group's name, description, number of users in the group and number of applications assigned to the group.

Adding New Groups

To enhance the user's role or access within the system, the Add New Button is prominently positioned. This option allows users to be added to more groups, expanding their access and functionalities within the application. The process is designed to be straightforward, guiding the user through a simple process to ensure accurate group assignments.

Editing Group

This menu option found within the ellipse (⋮) menu takes you to the groups page where you may edit any information related to the group

Removing Group Memberships

Equally important is the capacity to manage the departure from groups, which is facilitated by the Delete Group option. Also found within the ellipse (⋮) menu, this feature does not delete the group itself but rather unassigns the user from the selected group. This action ensures the user's access and permissions within the application are precisely tailored, maintaining security and relevance.

User Activity Log Page

This page shows user user-specific audit log for all the various actions and activities performed by the user. This may include all activities related to the user as shown below

User's Settings Page

Status: You can change the status of users and accounts in our system to manage access and control.

For Users:

  • Locked: Stops user access temporarily. This is used for security reasons or if there are too many failed login attempts.

  • Unlocked: Gives access back to the user, allowing them to log in and use the system.

For Accounts:

  • Active: The account is in use, and everything works normally.

  • Inactive: Temporarily not in use but can be activated again.

  • Delete: The account is deleted and moved to suspended accounts

Reset Password: A Generate button allows the administrator to reset passwords for users, which can then be copied to the clipboard if required.

RBAC: This section can be used to assign tenant-wide roles defined in the master to the user.

Secret Questions: This section shows a list of secret questions selected by the user

Additional MFA: Administrators can view the MFA mechanisms configured by the user as well as remove the configured MFA if required for a specific user

Trusted Devices by User

If Adaptive MFA is configured for users and a configuration for Device Trust is done, Cymmetri maintains a list of Trusted devices that satisfy the conditions of the Device Trust configuration. This list of devices trusted based on the configuration done by the admin are listed on this page with the following information about each device: Browser, OS, Created At, Trusted, Action(remove device)

User's Sessions

This page provides Cymmetri administrators with the capability to monitor and manage all user sessions, It provides the following information: Browser, OS, Created By, IP Address, Created At, and Action (delete session). A user may have multiple session entries if the Multiple Session configuration is enabled.

Managed View

The Managed View page shows the user data based on various provisioning applications assigned to a user, This page shows the Attribute Name, Managed System Value, and IDM Value

  • Attribute Name: Attribute name as defined in the policy attribute page of the provisioning application

  • Managed System Value: Value as saved in the provisioning application

  • IDM Value: Value as saved in Cymmetri

Delegation

In Cymmetri, one of the features available to users is the ability to delegate self-service access. This capability enables users to assign their access rights and responsibilities to other users temporarily. Ideal for scenarios such as vacations, business trips, or whenever a user needs someone else to manage their duties without forfeiting their credentials or compromising security.

This page shows the delegation provided by the user, this may be currently in progress or the delegation which was last completed.

The page shows the status of the Delegation (INPROGRESS, COMPLETED), Designated To, Start Date and End Date, and the list of Excluded Applications(if any)

Version
New Features
Fixes
Known Bug
Version
New Features
Fixes
Known Bug
Version
New Features
Fixes
Known Bug
Version
New Features
Fixes
Known Bug
Version
Version
New Features
Fixes
Known Bug
Version
Fixes
Known Bug
Version
New Features
Fixes
Known Bug
Version
New Features
Fixes
Known Bug
Version
New Features
Fixes
Known Bug
Version
New Features
Fixes
Known Bug
Version
Fixes
Known Bug

Please Note: User import process follows the synchronization policies as defined .

Type
Description

CIDR: Refers to the CIDR notation of the subnet of the network that this zone refers to. .

3.0.1 Beta (3 November 2023)

1. Policy Map Datatype Converter: Added standard converter to convert the LDAP profile picture. Added standard converter to encrypt & decrypt data.

1. Cymmetri Verify- When exporting TOTP users password is accepting all digits/values as alphabets/number when it should have accepted alphanumeric values

1. Manager notification: Receiving user name required manager name 

2. Decision Engine Restart Scheduler: Added scheduler which will run every hour and process stuck decisions.

2. Cymmetri Verify | IOS | Face ID being asked infinitely

2. Multi-role assignment with form, then form adding repeatedly for each role, expected only one form should be there 

3. Audit JMS Queue added for the following services, authPolicy, mfa, notification, provisionEngine, registration, ruleEngine, selfservice, usermanagement, workflow, IG, sodengine, pam, analytics.

3. Cymmetri Verify app- Showing duplicate records when imported from other device

3. Fido - Push/fido not getting removed from mobile app 

4. UI/UX Changes: Show Cymmetri Verify app link on push/fido registration screens.-Rejected for the selfservice app.

4. Cymmetri Verify app- Search functionality is not working when users imported from different device

4. Password converter only accepted encrypted value. It should also accept user's editable value

5. Cymmetri Verify App update (v5.9.1)

5. Cymmetri Verify- Show password when clicked and file is exported, then again export file same password is visible with no masking(password is visible)

6. Cymmetri Verify App update (v5.9.2)

6. Cymmetri Verify | IOS | Unable to import backup file

7. Cymmetri Verify App update (v5.9.3): Display a message to indicate the action being performed.

7. Cymmetri Verify | IOS | Face ID not supported error

8. Restructured bulk user import for performance

8. Cymmetri Verify | Account details not updated on adding/removing push/fido

9. Notification Global Config: Notification categories in two types i] Mandatory and ii] Optional. Notification Global Config applicable for only optional types of notification.

9. Cymmetri Verify | IOS | Not internet error

10. Application getting repeated within different pages of application list

11. My workspace>Access Review>IG>Managed - When all the checkbox of Info field are disabled, then title checkbox should also be disabled

12. User - Application - Group name should be displayed

13. Audit-Audit with device filter not working

14. Vaulting Configuration- Test connection audit not present

15. Notification Template- User is not receiving mail for reset password

16. Login-Showing incorrect validation message and asking user to reset password again

17. Onboarding flow | Additional details not accepting other country mobile number

18. Recon history- provide search

19. Tenant Registration- Domain is not visible

20. Register tenant- Country dropdown is showing no option instead of countries list

21. Application - Tag - Already created tags present in application are not getting displayed in grid page.

22. Partner Portal- Showing invalid argument but not able to understand exactly which field is invalid: Admin Portal- Top search not working Admin Portal- Get Started link not working Admin Portal- Company name and company code should get trim

23. Fido Authentication- User is not able to authenticate via FIDO in first time, user need to kill app or refresh inorder to register device

3.0.2 (1 December 2023)

1. User management service restructured.

1. Forgot password-User is not receiving email notification

1. Manager notification: receiving user name required manager name

2. PAM - Sub domain added in Authentication Parameter

2. Workflow description spelling correction

2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

3. UI/UX Improvements: Show username in user selection dropdown menus, Show Cymmetri Verify app link on MFA TOTP Registration and App MFA TOTP, Push, Fido, Show message when cookies are disabled on the browser Cymmetri Verify App update (v5.10): App drawer, header and lock screen UI improvements, Search box moved to header, Show search history, Haptic feedback on TOTP code press

3. Workflow on unassignment-On role unassignment, if any workflow already trigger then the message should be shown

4. Cymmetri Verify App Hotfix (v5.10.1)

4. Manage view- for converter used parameter not showing

5. Introduced spring expression language in SAML.

5. Application-date converter, recon pull getting stuck

6. In Multifactor otp config we can't disable both email otp and sms otp. At least one should be active.

6. Workspace | click search box creates Ul glitch

7. Group Provisioning

7. Login with Read only user- Configuration> Syslog configuration- Configuration should be gray out and should not be editable

8. Cymmetri Mobile App update (v1.5): Added QR code self-registration for TOTP, Push, and FIDO Added TOTP self-verification eliminating the need for finding and copying TOTP from the Cymmetri Verify app for the login. Added App lock with biometrics in the app

8. Configuration>User decommission config- Add a short description specifying functionality (Title)

9. MFA- Rename SMS Authenticator to OTP Verification

10. Configuration>Master>Zone>Gateway IP- Sorting is not working

11. Configuration>Master>Global>Value- Sorting is not working

12. Configuration>Master>Zone>Name- Sorting is not working

13. User Onboarding| Contact info details not accepting other country mobile number

14. Delegation- Successful Validation message should be shown after user is assigned

15. Time-based role assigned application- Time-based Application is not deleted after a period is completed when a role is assigned

16. Configuration>Master>Zone- Showing old zone data when creating new zone

17. My workspace>Access Review>IG>Managed - When all the checkbox of Info field are disabled, then title checkbox should also be disabled

18. Provision- When user is trying to create new role, role is not getting added neither validation message is shown

19. Cymmetri Verify - IOS - Push/FIDO Verification screen not shown when app opened through its notification

20. Cymmetri Verify - App protection not working

21. Self service app- User when trying to login on self service app having Fido authentication On, user is redirected to Play store but see in play store app is not clickable

22. Cymmetri Verify - Same day exported file - with file count attached to the name is reported as invalid file

23. Application provisioning MFA- When max TOTP/OTP/Secret Question invalid answers limit exceeds, it should show validation message and should be redirected to login page.

24. Application Role workflow- User is applying workflow for specific role but non-workflow as the signed role is also not getting assigned

25. Update user import sample file

26. usersrvc/api/user/dropdownList- in the above path, for creating workflow in bulk

27. when we create in bulk it is showing out of memory

28. Global Notification disable-by default it is off

29. Notification template- Global Notification for OTP is off still logs is showing mail sent(True)

30. Campaign with group-Campaign getting aborted

31. Multi-role assignment with form, then form adding repeatedly for each role, expected only one form should be there

32. Deprovision rule- User is not getting suspended when end date is applied at the time of user creation

33. Users Import- User name, Login should get trim if space is included while importing user

3.0.3 Beta (5 December 2023)

  1. WebAuthn passwordless authentication (It only works for chrome, safari, edge on desktop and chrome and edge on mobile) - EXPERIMENTAL

  1. Workflow for time-based role application- Audit log should show action not supported me ssage if lifetime application is changed to time base from approver end.

  1. Manager notification: receiving user name required manager name

2. Onbehalf Configuration: Default onbehalf configuration, Rule engine support to create custom configuration. Display the OnBehalf menu in self-service according to the logged-in user's matching custom/default configuration. Below menu operations supported: User Application View: Assign Application, Assign Role, Unassign Application, and Unassign Role. User Groups View: Assign Group and Unassign Group. Group Provisioning Enhancement Policy map datatype converter Enhancement. Converter support was added in the custom attribute. Configuration support added for custom attribute converters, Encryption added for Custom attribute password converter value of user, Cymmetri Verify v5.10.3 - (link) - Bug fixes Cymmetri Mobile v1.5.1 (link) - (Rejected): Bug fixes and Added self-verification support for forgot passwords, App MFA, server MFA, and passwordless. Global module search feature (Ctrl+K). Groups list pagination in user details, Connector: Oracle HCM, PAM: AD separated from the Cymmetri and Group - View Attribute - Showing list of CN of members of remote group

2. Recon Link for both exist- When updating the group after linking showing a custom attribute error

2. AD Group pull || Only under 1000 members getting pulled (Connector Server Restriction)

3. Multi node-Application assign with role, all user getting assigned but still import showing in progress

3. Application getting assigned from UI. If it is failed.

4. AD group count mismatch-In AD total 1278 group but in pull it is showing 1260

4. Group-Custom Attributes not getting updated in group while assigning user to the group manually

5. Application Group- Pagination should be applied for the group provision page

6. AD application push- Group should not be updated when update checkbox in policy map is unchecked

7. AD Recon Push- When all policy attribute are false, group creation should show error.

8. AD Application Pull- When all policy attribute are set to false, group creation should show error

9. AD-Policymap_memberOf need to be default false for old tenants

10. Browser specific-On Mozilla browser OTP verification is not proper

11. Login with Domain Admin- Manager assignments should not be greyed out

12. Import completed file show end time

13. Policymap-group(pull/push)-if attributes are inactive then this should not be reflected under dropdown

14. PAM-Sign on Policy- Policy should not get activated unless MFA factor is selected.

15. Audit-Configuration-OTP-For check uncheck Send OTP on,audit should be present

16. AD application- Should show error message when description is user principal

17. Self service-Read auto MFA considering camel cases

18. Cymmetri Verify app- Cymmetri mobile app is not able to fetch TOTP from verify app if the re are more than 20 TOTP users

19. Users Managed View- Managed view should get blank for those applications not supporting this operation

20. Configuration>Master>Browser Tab text is not correct

21. Workflow- Close button in Users details pop-up box should be enlarged (currently not visible properly)

22. Branding-Should show proper validation message on UI

23. Version-provisionsrvc showing two times

24. PAM> SignOn Policy- Discard button is not working

25. Identity Hub> Users: Others field details are not visible on user display page on editing profile

26. Cymmetri app(selfservice)-Auto read MFA-when Cymmetri verify app having App protection is enabled then also it is reading,bypassing app protection

27. Cymmetri Verify - Google Authenticator Import TOTP timer not running

28. Cymmetri Verify - MFA Push Registration fails

29. Cymmetri Verify - App crashing on Samsung fold phone

30. SAML-Expression-restrict to show id

31. SAML-Expression-if user don't have data and fetching data then no message showing on UI

32. SAML Key:- Not able to understand why validation message is showing invalid arguments

33. Delegation- Session getting expired even after refreshing token continuously

34. External idp login showing error

35. SAML-User is not able to download metadata, showing 500 internal server error

36. API SSO validateToken API only validate the auth_key parameter

37. Password converter only accepted encrypted value. it should also accept user's editable va lue

38. Identity Hub>Group: Grey out Group name field for remote groups as user cannot edit name

3.0.4 Beta (3 January 2024)

1. Connector: Darwinbox and SuccessFactor

1. Reset password OTP- Max limit validation message should be displayed if 3 invalid otp are provided

1. Manager notification: receiving user name required manager name

2. Cymmetri Verify now supports webauthn QR code scanning from mobile in case mobile camera doesn't support QR scanning

2. For the newly created tenant configuration showing error

2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

3. Persistent Form Enhancement: Added Form submission support on Role assignment, Added Form submission support on Role unassignment and Added configuration to enable/disable form submission on role assignment and unassignment.

3. For newly created tenant notification template not loading

3. Workflow initiated for form but form is getting updated without workflow approval.

4. Policy Map Data Type Converters: Added support to input pattern of date of target system and Added support to convert date & date time of target system using mentioned pattern.

4. Time-based/Normal Application- When deprovisioning time-based application or successf ully assigned application is going into failed state showing null pointer exception

5. PAM: Download AD Certificate

5. Selfservice-Behalf-User-Group-Group is already assigned then also it is again available for t he assignment

6. Passwordless Login Flow Enhancement.- Now tere is MFA registartion is optional in login

6. Selfservice-Team-User-Group-Group is already assigned then also it is again available for t he assignment

7. Lock user on mfa failed Attempt: Added configuration for mfaattempt, coooldown period.

7. Group-Custom Attributes not getting updated in group while assigning user to the group manually

8. Provision Rule- User need to refresh page when adding/updating application role condition

9. Recon pull with AD-For default data related to date it is not working

10. ctrl+K search -add MFA rule not present

11. Partner portal-Add customer with domain-for domain field validation should be as per the normal registration

12. Cymmetri verify App(Selfservice(-Need to handle auto register flow in the application MFA

13. App Auth does not work when verify app in closed state

14. ios 17.2 Auto Auth not working

15. ctrl+k search-Read only user redirecting on add form

16. SAML-Expression-Provide sample on i icon

17. PAM- Rename server to device

18. Login with PAM Read Access Admin-PAM>Devices>Setting: User is able to edit complete p age details and showing processing validation message when clicked on save button

19. User not getting deleted from AD when assign in AD

20. Recon-Pull-Group, for one user having 900 groups, then under recon history showing error,same vice versa one group multiple users

21. Take pull from AD- User having remote group present in AD

22. When password is expired and the user is trying to change password then it is not adhering password policy, accepting same old password

23. SAML-Regular expression-if user entity not exist and doing SSO then in audit data should be present

24. Identity Hub- Group: Validation message should be shown when clicked on assign group button

25. Identity Hub >User: Custom attribute dropdown is not completely visible

26. Custom Attribute Import- When the password attribute is imported via csv file then password should be visible in encrypted form in user details

27. Custom attribute Import via API EXT- Password should be encrypted form when imported

28. Application MFA- Showing routes issue when accessing application

29. Not able to login on partner portal via admin login

30. Route issue-On click configuration tab

31. On Behalf- Route issue

32. Import> Download sample file- showing route error

33. Browser cookies disable-end user-facing difficulty

34. Calendar: Resolution specific> Calendar Ul is getting glitched at 75% 80% 90% zoom

35. Identity Hub-Users: User should not be able to assign application again if already is assigned.

36. Teams-Add user showing unknown error

37. Inbox showing unknown error

38. Teams-User list not showing

39. Application Recon- When user is trying to Pull users from database and if pin code is blank, then default set value should have been taken

40. Authentication> Auth rule- Showing Rulesrvc not found validation message

41. Policy map update-on save showing error

42. Hide this /disable button when script is enabled

43. MFA- Rename SMS Authenticator to OTP Verification

44. Application getting assigned from UI. If it is failed.

3.0.5 Beta (12 January 2024)

No new features were introduced. This version has implemented all the features and bug fixes from the 3.0.4

3.0.6 Beta (30 January 2024)

1. Provision Rule Revamp: Restructure Provision rule condition configuration: Provide support for single condition and group condition in condition config, Provide Operator support like Equal and Not Equal and Provide AND, OR Operator support for multiple condition in provision rule condition config, Group provision Support: Add group in provision rule. (only local group), Old provision rule migration: If the old rule is without condition mark it as inactive and if the old rule is without application also mark as inactive.

1. Provision Rule- Rule is not getting applied if previous provision rule is deleted.

1. Manager notification: receiving user name required manager name

2. UI/UX Changes: Application profile and group mapping in SAML SSO and SAML Service Provider - Restructuring and provide defaults

2. Group- Search functionality is not working

2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

3. Deprovision Rule support for user delete (if no application assign)

3. Not getting form values in the target application when Form updated, role assigned and role unassign

3. Workflow initiated for form but form is getting updated without workflow approval.

4. SSO -SAML: SSO-group policy Mapping -- SSO SAML, SSO-added nameFormat in profileMapping and groupMapping -- SSO SAML. SSO-added digest algorithm method. SSO-added list support for profile mapping.

4. Self service app- Increase spacing

5. Mfa Attempt Enhancement(Old behavior when admin locks the user then the user should not able to unlock from selfservice now he/she can able to unlock yourself): User can unlock if admin locked the user invalid mfa will permanently lock the user, user can unlock account after mfa cooldown period is completed. Admin can unlock the user which will unlock the mfa as will.

5. Notification bell icon- When notification is empty, mark read and delete option should not be clickable

6. UserType Master Support in User Creation and Updation.

6. Cymmetri self service app- When clicked on groups or application from on behalf tab, it is redirecting to dashboard page

7. User Onboarding| Contact info details not accepting other country mobile number

8. Cymmetri Verify app- For long tenant name timer clock is not visible

9. Group-Attribute detail-provide search

10. Android Heads Up Notification now will display notification upfront which earlier required from user to turn on from the Notifications Settings (Float Notification)

11. Notification template-correct spell for delegation

12. Deleted user login-on forgot password this user should be validated and restrict,currently showing error-Please try again

13. SAML-On clicking validate regular expression should show data message which is available in backend

14. Ctrl+K: Search filter is showing records for all the letters mentioned

15. If the admin lock the user, then the user should be able self unlock by forgot password flow

16. Audit- Audit log should shows role specific logs for role assignments/ unassignments

17. Self Service: Access review- Validation message is not complete it is getting cut

18. Registration- Showing processing please wait validation message after registering user and without any setup if user is clicking logout

19. Self-service app-On behalf: When clicking on application/groups from the dropdown mobile keyboard is getting displayed and due to that applications/ groups visibility is less

20. Not getting form values in the target application when form updated, role assigned and role unassign

3.0.7 Beta (09 February 2024)

1. PAM SUDO SU feature for linux server.(For SUDO SU shortcut key Ctrl+Shift+E)

1. Default delegation consents do not convey responsibility of delegator or delegatee

1. Manager notification: receiving user name required manager name

2. SAML Assertion Preview

2. Self service app- On behalf: When clicked on application/groups from dropdown mobile keyboard is getting displayed and due to that applications/ groups visibility is less

2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

3. Encrypt saml response

3. Provision rule-On click save showing error,without condition

3. Workflow initiated for form but form is getting updated without workflow approval.

4. ETL: Custom Create user in AD API with unboundid library, Custom user assign to group in AD API with unboundid library

4. Configurations-general-config-Rename message for User Decommission Config

5. Configurable UI Info and Actions: Hide "Reset / Unlock User", Hide "Login Help Page Link", Configure "Login Help Page Link", Hide "IP Address" and Hide "Self-Service App Links"

5. Label update for suspend config

6. Login Help page external link updated

6. Provision Rule; Groups/Application- If user is selecting any local group in first field then second field is greyed out not showing other local groups

7. Cymmetri Verify: Firebase version upgradation and A troubleshoot page provided if FCM token is missing

7. Notification content should not be hardcoded

8. SSO UI migration

8. Remove trailing slash from selfservice endpoint

9. Made Gateway IPs and Proxy IPs non mandatory on the Masters -Zone page. Only Name and CIDR fields will be mandatory.

9. Error handling for product Webhook custom error

10. Application SSO-attribute mapping-without selecting Cymmetri Attribute save button should not be enable, as this is mandatory field

3.0.8 Beta (23 February 2024)

1. UI/UX Changes: Skeleton loaders - Improved loading indicators, Filter enhancement for Users and Application pages - Now filter persists the data once go in the detail page and comes back also an indicator to show how many filters or any filters are applied and Branding changes - Now the preview of branding will be on scroll for better UX , "should help icon be shown " field would highlight the help icon

1. API Integration for passwordless flow reset password

1. Manager notification: receiving user name required manager name

2. Mfa attempt Admin User lock:Mfa attempt config added in global auth policy, Self-unlock flag to unlock the user during admin lock the user and Email for invalid mfa attempt

2. Workflow- For the user list workflow approver, the user is showing in the list dropdown but in the pending workflow it is showing empty.

2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

3. Service Provider (SP) Initiated SAML Single Logout

3. Application- Application name should be unique

3. Workflow initiated for form but form is getting updated without workflow approval.

4. Secret Questions verification changed: Earlier it used to show all questions and mandate the user to fill in all the configured questions. Now it will only ask the user to show a dropdown multiple times configured by the admin for minimum correct answers.

4. Applications Group mapping- Change the validation message as only one group can be added in group mapping/ disable the add attribute button after 1st group mapping is done

5. SBI VAPT: Encrypt 'login' in some public API same as password encrypted. The following APIs are changed: validateIdentity API: on login page, validateIdentity API change get type to post and in request body login encrypted value pass and token API: on login page token api login encrypted value pass.

5. AD application Recon- When importing users via recon having provision rule assigned for User creation with condition, then showing error in recon history and again after executing run now command then the user is getting imported but going in Ignore case.

6. AD Application recon- When workflow is applied for User creation having condition applied(Department=Accounts), and user is imported via recon, recon history is showing user assigned but when searched In identity hub-Users, showing user not found.

7. Notification Template- Showing processing please wait message when trying to click toggle button

8. Provision Rule- User should not be able to save provision rule without adding applications/groups

9. SBI VAPT || Testing and changes for SBI as well as product

10. Application SSO- Label change to update

11. My workspace>Inbox- User details popup box should not be displayed when user is deleted from admin account after initiating workflow

12. Deprovision- Remove Exclusion Applications field

13. Delegation account- Change label from Delegate Session Active to Delegate Session Information

14. Users> Applications- The total number of applications assigned should be shown in user account

15. User: Menu Action- There should be a sync event toggle button while marking user inactive in user menu as available while marking inactive from user setting tab

16. Policy attribute- When removing the policy attribute, that field is not getting removed also it is visible in policy map application field dropdown

17. Identity Hub> Users- Users should be searched on basis of Usertype as well

19. User Creation Workflow- When clicking on the cancel button on the workflow preference popup box, it should remain on the user creation page. For now it is cancelling the whole process

20. Application> SSO>Configuration>Edit configuration- UI for logos and name is not proper

21. Application SSO> Configuration- The marked button should be disabled until service provider is selected

22. Branding- Change the label as both the fields sound similar

23. Branding- Preview is not available after changing setting

24. Branding- Add a short note/sample file for default help link when show help button is Yes

25. User Filter- Reset button should reset all the filters applied and load complete data

26. Self Service App>Managed access- Fields on right side should be slightly moved to left as in mobile it is not visible properly

27. Application Audit logs- Applications are getting updated when password reset is performed for users.

28. Selfservice app-MAX MFA attempt message is not readable

29. Self Service mobile app: Application- Application Tag is not visible when clicked on move to tag option at first time and later on option is continuously visible

30. My workspace> Inbox- Starred requests are not getting saved in starred folder

31. Exclude application > delegation- When any application is added in tag and excluded by delegator, then should not be visible in delegatee account

32. My workspace: Application- One application should be assigned/moved to one tag only

33. Teams Configuration- Showing route issue when saving new teams configuration

3.0.9 Beta (03 November 2023)

1. Provide show-to-user flag support in the Application Setting. Application Setting: Show to user: if the flag is off, then hide the application from my access ➝ assigned application. Delegation: If the flag is off, hide the application from Delegation ➝ my access ➝ assigned application. user can request: If the flag is off, then hide the application from my access ➝ request for assigned application, If the flag is off, then hide the application from On-behalf ➝ users ➝ request for assigned application and Delegation: If the flag is off, then hide the application from Delegation ➝ On-behalf ➝ users ➝ request for assign application.

1. Policy Attribute- Add pagination

1. Manager notification: receiving user name required manager name

2. Framework Upgrade: Java based services are updated for spring framework, spring boot, also updated utility libraries. Please note it may have impact on several functionalities.

2. Teams Configuration- Showing route issue when saving new teams configuration

2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

3. MFA attempt Admin User lock: MFA attempt config added in global auth policy and Self unlock flag to unlock the user during admin lock the user

3. Passwordless- Passwordless page is showing blank when clicked on clicked on Passwordless button on Login page

3. Workflow initiated for form but form is getting updated without workflow approval.

4. Token Rolling period : Token start period should start before current server time.

4. Notification template- Increase spacing between Kathreftis Team and Disclaimer and remove space above

4. In application setting if show to user flag off then also application show in recent application.

5. Passwordless reset password : When password is required to be changed then user is forced to change password during login using passwordless.

5. Login failed> User locked Template- Change notification template

6. Bearer Token subject is encrypted now in header.

6. My access> Applications- If an application is already present in a certain tag, when attempting to move it to another tag within the "All Applications" section, it should not be visible in the tag it is already associated with.

7. cookies samesite attribute is being set to strict to all the cookies.

7. Login-Tab button should be applicable for enter password field when passwordless in enabled

8. Active Directory new bundle (Using unboundid.ldap.sdk library) - Phase 1: Server Connector bundle name: simpleADServer Connector bundle version: 1.0Server Connector name: com.cymmetri.connector.simple.ad.SimpleADConnector and Added one field inside the user configuration of the active directory "Disable User With Date Time".

8. AD Application- When assigning remote group to AD user, showing error

9. Passwordless- Passwordless page is showing blank when clicked on clicked on Passwordless button on Login page

10. Self-service app: On-behalf tab is loading late

11. Master> Zone- When editing zone then status is always changing to inactive

12. Authentication Rule- When a user is trying to reset the password having LDAP authentication active, then password is changing into target system first and reflecting older password in target system

13. PAM- Dormancy disabled config- By default config should be disabled

14. Audit-"action":"DORMANCY_DISABLE_COMPLETED" ,Data showing null,need to show data

15. PAM dormancy disabled showing failed

16. Deprovision- All three fields should be in one line

17. Policy Attribute- Add search filter in policy attribute

18. Delegation- Add cancel button after editing consent

19. My Access> Applications- When moving an application from one tag to another, the validation message should be proper for the end user to understand

20. Campaigns> Access Review > Campaign Manager- Sorting is not working

21. My Workspace> Inbox- Need to refresh page every time to see changes in started request

22. Global Auth Policy- Update message to "Auto Unlock MFA period should be less than Account Auto Unlock period."

23. Insights> Reports -Showing error message when disabling scheduler toggle

24. Application MFA update -on click Next button -getting in loop

25. PAM vault user-Confirm button should not be enable till any value entered

26. Validation message change-Change 1 days to 1 Day

27. Teams Config- Configuration should not be saved without adding condition

28. Teams - User is not able to lock/unlock account even after configuration in teams is enabled

29. Need to show proper error message when Maximum MFA attempts reached

30. Reset Password OTP -there is only OTP option is available then also showing error message for question

31. MFA- User not able to login via Consent based MFA showing error

32. Login- Showing error when trying to log in using secret question as MFA

33. Teams Configuration- Showing route issue when saving new teams configuration

34. MFA count gets reset, when admin mark lock to unlock

35. MFA- User is able to unlock account event after unlock user account time is not completed

36. Login with password less-password expiry should be consider and need to follow steps to reset

37. When admin lock user the take conformation, unlock yourself or lock lifetime

38. End date over user login-on forgot password this user should be validated and restrict,currently redirecting on MFA

39. Inactive user login-on forgot password this user should be validated and restrict,currently redirecting on MFA

40. Need to update audit when user attempts max MFA

41. MFA- User not able to login when user is trying to login using normal password flow

42. My workspace> Active Campaign- Latest selection should remain as it is.

43. Pagination persistence for users (when a user clicks on lets say 3rd page and go into the user details and when come back the pagination gets reset )

44. Application provisioning workflow- Assign application to user and then cancel it, still showing user assigned

45. My Access>Application> Tag- Search filter should be applied for tag applications as well

46. Add New Application Search, when no data is there the UI breaks and a No Data Found card should also be shown on screen

47. Login Page- User is not redirecting to mentioned login help page( Mentioned in Branding)

48. Cymmetri Mobile App- Changes required in secret question layout on login page

49. User Creation Workflow- When clicked on the cancel button on the workflow preference popup box, it should remain on the user creation page. For now it is cancelling the whole process

50. Branding- Show validation message if user miss to fill any fields and clicked on save button

51. Lifecycle mgmt>Workflow Configuration- Save button should be enabled when removing approver.

52. Suspend user-For device deleted message should be shown as Device Deleted

53. User Onboarding- When provision rule is trigged while onboarding user and any application is assigned to user then assigned tag should be shown in that application as showing in Groups

54. Configuration> Master- Accepting emoji values in Global Master

55. MFA- Secret question- Answer field should get blank after question is selected.

56. Delegation- After delegation time is completed, delegation configuration should be updated

57. Authentication Rule- When user is trying to reset password having LDAP authentication active, then password is changing into target system first and reflecting older password in target system

58. Global Auth- User should be able to set Account unlock and MFA unlock to minimum 1min

59. User-Account lock-Account is self lock then also on UI showing message user cannot unlock

60. User Setting- Showing user not found error message

61. Lifecycle Management || Applications redirects user to Identity Hub

62. Campaign- UI of Calendar field is not proper

63. Policy attribute- When removing policy attribute, that field is not getting removed also it is visible in policy map application field dropdown

64. Audit Log- When duplicating a tab and subsequently refreshing it, then audit log is displaying a random requestor ID

65. Global Auth Policy- "Allow Users to have" is displayed twice

3.0.10 Beta (21 March 2024)

1. Addition of Grade as an attribute for users: Workflows updated to support grade-based approvers: Added grade to Pending Workflow Page and Workflow List Page, Added grade for User profile: Added grade in create user, update user, user info page, grade in user info page for Suspended Users and Archived Users and Displaying grade in User Details [Assignee Details], Added grade in Attribute Setting, policy map [cymmetri policy mapping drop down], bulk import and Added grade in Teams Config Page: Added grade in create user, update user and user info page, grade in user info page for Suspended Users and Archived Users, Added grade in OnBehalf config for self user, Displaying the grade for self user profile, Added the grade for the pull/push reconciliation process Added the grade to get the value of the middle name in a user profile, to create the user through apiext, Added grade in JIT to create the user -Not working and Added grade value on the page that displays the delegatee.

1. Application Update Workflow- In inbox user name and Login ID fields are showing empty

1. Manager notification: receiving user name required manager name

2. Analytics Metabase in the report: Configuration of Metabase and Metabase Report

2. Rename application name as shown below should be Google Workspace and not Google Workplace.

2. AD Group pull || Only under 1000 member getting pulled (Connector Server Restriction)

3. __MANAGER__ support in policy map for manager assignment in Active Directory (Target application)

3. Fix typo in application provisioning labels

3. Workflow initiated for form but form is getting updated without workflow approval.

4. Addition of Middle Name as an attribute for users: Added middle name in create user, update user and user info page, in user info page for Suspended Users and Archived Users, for User Profile, to Pending Workflow Page, to Workflow List Page, Displaying middle name in User Details [Assignee Details], Added middle name in Attribute Setting, Added middle name for the policy map [cymmetri policy mapping drop down], for the bulk import, in create user, update user and user info page, in user info page for Suspended Users and Archived Users, in OnBehalf config for self user, Displaying the middle name for the self-user profile, Added the middle name for the pull/push reconciliation process, to get the value of the middle name in a user profile, to create the user through apiext, in JIT to create the user -Not working and Added middle name value on the page that displays the delegatee.

4. Preference Workflow config popup box - Add Auto option in dropdown list when workflow approver is set to user list

4. In application setting if show to user flag off then also application show in recent application.

5. Role Required in Application Assignment: In the application setting, Role Required flag added and Application Assignment flag is enabled in the below mentioned pages:Application assignment page, User page, in application assignment and Self-Service: When user request for application, Teams page, in application assignment and Onbehalf page, in application assignment.

5. My access application- Calendar UI is not proper for 90% resolution

5. Creating the user through the JIT: Message was rejected due to issue instant expiration

6. Password policy-Show last sync time if already sync

7. MFA attempt configuration-take confirmation on save

8. JIT-Detail showing route error

9. JIT-Custom field-Only type=USER should be present in dropdown, currently showing group also

10. correct notification template-login failed

11. Unlock User- API is getting called twice and login should be shown in encrypted form

3.0.11 Beta (05 April 2024)

1. New Feature - Amaya (Schema Maker): A new feature called "Amaya" is released for generating policy map, policy attribute, and also for generating schema for various functions - Create User, Update User, Sync User, Search User etc. Using a UI-based designer, an administrator may configure JSON REST-API based applications without needing to write scripts for the above mentioned functions.

1. Inbox- Request count should be shown in claim> open request as visible in Requests>Open request

1. Manager notification: receiving user name required manager name

2. Role Required in Assign Application(Backend Validation):Bulk Application Assignment, Admin Application Assignment, Admin User Page, Selfservice, User Application Request, Selfservice -> Teams, Application Assignment, Selfservice -> Onbehalf and Application Assignment

2. Application deprovision Workflow- When removing role from user application, workflow is getting triggered but before saving popup box is getting disappeared

2. Workflow initiated for form but form is getting updated without workflow approval.

3. Active Directory new bundle (Using unboundid.ldap.sdk library) <Group operation supports>: Added a field inside Active Directory User Configuration Page: "Add or Remove group using Simple AD".

3. Password Policy- Accepting -1 in password history versions and also displaying in policy rule when changing password

3. In application setting if show to user flag off then also application show in recent application.

4. Added a default filter for the start date as the current day in all report detail views.

4. Password Policy- Password history versions should have default 0 value and also add note specifying description of 0 value.

5. The view button in the application role is only visible when edit access is not provided to the user, but read access is granted, such as for read-only users.

5. Import user with grade,need to handle user import with inactive grade

6. PAM - Device Termination when device unassigned

6. Attribute setting- Not able to disable grade attribute

7. Audit log- Showing application id instead of application name when moving application to tag from self service app

8. AD Authentication- Audit log should be shown when changing password for AD authenticated user

9. My workspace >Teams>Users- The message "User account locked" appears whenever changing pages.

10. Forms- Field name is not displaying double spaces when inserted in JSON field

11. Workflow Config- Add Remove button for stage 1 user

12. Tenant registration flow- show password not working

13. Workflow- Pending/ Inbox- Menu action should not be visible for every application or when field is empty.

14. Identity Hub>User Filters- When applying a filter for inactive users or any other filter and then activating the same user, the filter selection is removed, but the count is still displayed.

15. Upload CSV- Not able to drag and drop csv files in import users, manager assignments, groups

16. Global module search-when product is disabled and the user trying to search then showing an error

17. Application update Workflow- Workflow is not getting trigged when application role is assigned to user

18. Partner portal-delete customer not working

19. Applications-For old google applications name getting replaced with Google Workspace

20. Password Policy>Blacklisted Password- When setting blacklisted password for user showing error

21. Password less login showing error

22. Email Notification- User is not receiving email notification

23. Version Specific > Delegation recent apps- When the delegatee is accessing the account then excluded applications are still showing in recently used apps

24. Admin MFA -on click save showing error

25. TEAMS-Menu action click showing unknown error

26. Admin Dashboard, Risk Dashboard and Insight reports are not loading

27. Taking time to load data in complete application

28. User-Activity -taking time to load data

29. AD- Recon- Push- Users are going into pending state for new AD bundle

30. Managed View- IDM value is not getting displayed

31. Notification template-need to add middlename attribute under system variable

32. Users | Sort by filter should be beside Sort Order

33. Role mandatory-In import assign application there is no validation, without role also able to assign

34. Identity Hub>User>Setting- Admin should not be able to lock himself from setting

35. Suspend user-for AD update , remove application

36. AD application - In Suspend user, application status is showing fail updation state

37. Group-Recon pull-update and full sync assign/update-taking too much time

38. AD Group pull || Only under 1000 member getting pulled (Connid Restriction)

39. Remote group-bulk assignment showing error, "failureReason" : "javax.naming.ServiceUnavailableException: [LDAP: error code 51 - 0000200E: SvcErr: DSID-031A1202, problem 5001 (BUSY), data 0 ]; remaining name 'CN=allgroup,OU=allgroup,dc=cymmetri,dc=in'"

40. When Add group pull/push then server getting stuck due to memory increase.

41. Remote Group assign in bulk-Not moving all user in group under AD

42. AD Application new bundle- If user is inactive in AD, and same user is updated in Cymmetri then user in AD should also get updated

43. AD Recon push-User not getting push in target (New bundle)

44. Adaptive MFA-Blacklisted ip configuration- Not able to enter range

45. Phone number - Phone number and country code validation issue

46. Partner portal- Company name letters should be extended to 100 characters and space at the end should be trimmed

47. Partner Portal- On the admin approval dashboard page, column name width should be identical, and if the name is extending then the extended name should be shown in hover.

3.0.12 Beta (18 April 2024)

1. Upload filename length validation: When a file is uploaded in the form of a profile image or Excel file import then validation is added for the file name length. Implement pages are as follows (20 characters): Selfservice profile picture, Application image, and Excel upload in User import, manager assignment, application assignment, group assignment,Role import

1. Application> Roles- Add toggle button to Active /Inactive status.

1. Manager notification: receiving user name required manager name

2. For the remote group, when a user or application is assigned to the group, they will not be assigned to Cymmetri until they have been successfully assigned to the target.

2. Add application/device name with space,Space should be trim

2. Workflow initiated for form but form is getting updated without workflow approval.

3. Workflow Config: After creating work flow now user redirect to workflow config page and Now we can't active workflow if approver not configure in workflow config.

3. Users> Activity- Filter and search should be added in user activity

3. In application setting if show to user flag off then also application show in recent application.

4. Workflow-"Save" button should remain disabled unless some condition is mentioned

4. Unable to identify application properties data type where value is empty

5. Application SSO-attribute mapping-for duplicate entry, a message should be shown on the same screen, refer other modules for the duplicate entry error message

6. Lifecycle Mgmt>Hook Config - Search filter is not working

7. Amaya Connector- Show complete name on tooltip

8. User Setting- Change validation message for all three tasks( Active, Inactive, Delete)

9. Workflow Configuration- If the approver is not present then workflow config should not get active

10. Partner Portal - Add Asterisk (*) for marked fields

11. Partner Portal- The validation message indicates that spaces are acceptable, but the field is not currently allowing them

12. Partner portal- Company name letters should be extended to 100 characters and space at the end should be trimmed

13. Amaya-Param getting duplicate

14. Trigger email to user when MFA max attempted in login

15. Master > Audit logs- Audit for fields created or updated in Master is not showing except for Grade

16. PAM Device- Not able to search PAM devices from my workspace

17. Application add with space,Need to handle space in backend also as temporary fix deployed from UI side

18. Rename- Dynamic json connector to Amaya

19. Amaya connector- Rename Dynamic Json connector to Amaya

20. Dynamic Json Connector- Text is overflowing tag border

21. Delegation- User should not be able to save delegation when start date is in past.

22. Amaya-policy map-felicity-If for policy map attribute not generated then default value should be there

23. Add application-For policy map default should be off

24. Update pagination offset - label and placeholder

25. Amaya-Response getting hide

26. Rename Amaya provision sub tab to User Configuration

27. Amaya-Policy map,tooltip overlap issue

28. Partner portal-under cymmetri customer total user count showing-1, actual available-12

29. Recon- Modes should be non editable

30. Import users via CSV/recon- Users should not be imported/ should show error when particular usertype, department ,designation fields are inactive

31. Load Test Data: Identity Hub> Users- Pagination is not working when multiple users(Load) are present

32. Workflow- Workflow popup box is showing unknown but in pending workflow is going into requestor manager

33. User-Filter with custom attribute not working on below data

34. AD Application new bundle- If user is inactive in AD, and same user is updated in Cymmetri then user in AD should also get updated

35. AD Recon push-User not getting push in target (New bundle)

36. Recon- Timing is not correct

37. Application delete-Deleted application present under Provision rule, even after application deleted

38. Processing please wait message should be changed, when no data is entered and clicked on preview assertion

39. Deprovision- User is getting suspended when the deprovision rule is executed via scheduler when no end date is applied or status is inactive

40. Reports> Filter- Showing error message to enter start and date when resetting filter or applying any other filter.

41. Remote Group assign in bulk-Not moving all users in the group under AD

42. To verify user deleted from AD OU and cymmetri admin trying to assign remote group

43. AD application - In Suspend user, application status is showing fail updation state

44. Remote group-bulk assignment showing ServiceUnavailableException

45. Group-Recon pull-update and full sync assign/update-taking too much time

46. Ad Application- Application assignment is going in failed state , but deleting application is also getting failed

47. Assign user to remote group is failed

48. AD application recon- When workflow is configured and recon is executed, then user is going in pending workflow

49. AD New Bundle- Thumbnail Photo is reflecting incomplete(In hex form) in AD

50. Workflow- Workflow popup box is showing unknown but in pending workflow is going into requestor manager

51. Recon-Name not present then also showing error for the duplicate

52. AD application - In Suspend user, the application status is showing a fail updation state 

53. Custom attribute Import via API EXT- Password should be encrypted form when imported 

54. SSO-Openid not working on QA, same working on dev 

55. Multi node-Application assigned with the role, all users getting assigned but still import showing in progress 

56. API ext (API Client) User not getting created 

57. Deprovision rule-user data not getting updated when changing Grace Period from 3 to 0 days 

58. Unable to add Gmail account on Android after logging into Cymmetri 

59. Tenant specific> Reset OTP config- Not able to save configuration 

60. Partner portal- Display validation message specifying some fields are missing 

61. Grade workflow- Preference config popup box is showing the user name but pending is showing Unknown 

62. Group recon pull-when space is in name then not going in ignore case 

63. Workflow- Sequence for approver is mismatched in the preference config popup box and pending workflow 

64. Workflow- Workflow in the preference popup box is showing the user name but in pending showing unknown when applied for user list or grade 

65. Workflow- When approver is set as reporting manager and application workflow is initiated then preference box is showing approver name but pending is showing unknown 

66. Schedule report- cron not getting updated, from hourly to change once in day then also report receiving hourly 

67. creating the user through the JIT Message was rejected due to the issue instant expiration 

68. PAM device is assigned then on access showing a message for the disconnected 

69. AD Adaptor token- Token is showing Invalid 

70. PAM Device- showing processing plaese wait validation message with 403 forbidden error 

71. Application- Showing processing please wait validation message. 

72. Loadtest-workflow page not loading 

73. Expired session: Showing blank page when clicked on user setting logout tab 

74. Suspend Config- User should be able to disable suspend config 

75. Deprovision- Deprovision via scheduler is not working 

76. AD-Recon pull with update-If user data removed from AD and taking pull,then this data not updating in the cymmetri user data 

77. group push-not taking user in AD at the time of update 

78. Daily scheduler running late 

79. AD Application- Showing error when trying to update profile picture 

80. MFA- Rename SMS Authenticator to OTP Verification 

81. Global Auth- When the "Single Session > Block Session" setting is enabled, attempting to log in with the same user account should block the user even before verifying Multi-Factor Authentication (MFA). 

Country

Country key-value pairs are stored in the system, and are available as drop-downs wherever needed in the system - User attributes, Policies and other mappings.

UserType

UserType is used as one of the conditions while defining authentication policies and as an input in the rule engine.

Department

Department is used as one of the conditions while defining authentication policies and as an input in the rule engine, and also as a user attribute.

Designation

Designation is used as one of the conditions while defining authentication policies and as an input in the rule engine, and also as a user attribute.

RBAC

RBAC (System Roles) is used as one of the conditions while defining authentication policies and as an input in the rule engine, and also as a user attribute.

3.1.6 -Beta

New Feature

  1. Logic - The FormLogic functionality, enables you to store custom data using flexible, administrator-defined forms. It empowers you to create forms tailored to your specific data collection requirements, providing a versatile solution for various data management needs.

  2. 360 Degree Reconciliation - Compare tab added to the current feature, where the user can compare with the source application and target application and further generate reports and download CSV.

  3. SkipPasswordExpiry - We are enhancing our Password Policy by introducing a new field, SkipPasswordExpiry, within the PasswordChangeRule. This enhancement allows users to opt out of the password expiry process entirely. When the SkipPasswordExpiry field is enabled, users will not receive warnings or notifications about password expiry, nor will they be prompted to change their password due to its expiration.

  4. Connector a. SimpleLDAP application

  5. ICICI Client - Role-Based form delivery in IGA.

  6. SDK-based integration to send mobile push notifications to mitigate legacy API issues: a. Fido Based Notifications b. Normal Push Based Notifications

  7. The LDAP adapter has been updated with a new feature that eliminates the need to enter a username and password for each execution.

Fixes

  1. Time-based Application: Timebased application assignment message spelling incorrect

  2. Deprovision- When applications are assigned via group and deprovision is executed all the applications should get deleted.

  3. Teams - Suspended Users - List View - Edit - It is redirecting to Users but showing blank screen

  4. Application Search: When clicking on "View More Applications" and searching for an application, the application is not being found.

  5. Pending Staging- When no records are present on the page, the "Select All" button should be disabled like the other buttons.

  6. User Onboarding - Dropdowns are not loading when creating a user after adding an Admin during the registration process.

  7. Global search - Pending action is not coming in global search

  8. Form logic-Configured Forms -On click setting icon screen getting flicker

  9. Selfservice Submit form-Update error message and backend error code if pre and post hook script having error.

  10. Form logic-on form submit close form

  11. Form logic-Selfservice-My Form Submissions pagination, page getting blank

  12. Archived Forms detail-Revision data showing wrong, showing non existing list

  13. Form logic-After changing form schema, form detail showing blank

  14. Form logic-User submissions-Provide search by taskeid,username,loginid

  15. Form logic-on all screen search only working for the exact case, expeted should be work for matching cases

  16. Form logic-Form table-sorting not working

  17. Form logic-Pre and post hook should be non mandatory

  18. Form map with rule-if form map more than defined limit then error message showing only one time

  19. Staging users details - Version history log user details not loading

  20. Form logic-Configured form and archive form detail, back button behaviour is not as ex[ected, need to click multiple time.

  21. Form logic-Form Access Rules-Link form, save button should be disabled till form selection

  22. form logic- if request is timeout or fail then feature showing diabled

  23. Form logic-User submissions-Provide date filter

  24. Workflow || Additional Form Info || Readonly text-based form submissions

Internal IDP

Authentication

CIDR Notation

External IDP

Delegating Work to Delegatee

Delegate Work to Delegatee

Following are the steps to delegate work to a delegatee:

The logged-in user needs to go to their Settings Page by clicking on the user's username on the top right

Once on the Settings Page user needs to click on the My Delegations menu

Toggle Status: Enable the Toggle Status to Active

Start Date: The date from which the user is delegated the work

End Date: The date up to which the access is delegated

Delegated To: The user (delegatee) to whom the work is delegated. This dropdown populates the list of all users to whom the task can be assigned

Excluded Applications: List of applications whose access is not provided to the delegatee

Once all the details are filled the user is expected to accept the consent to be able to configure the delegation. The consent looks something similar to as shown below:

Once confirmed the user needs to click on the I agree check box and save the delegation.

Once saved the delegatee can see and accept the delegation in their My Delegation Page under Settings.

Setting up Delegation

Delegation as a process in the Cymmetri platform refers to the ability of any end-user to delegate their responsibilities to any other end-user on the platform. As such, delegation provides the ability to the delegatee to perform various actions, including Single Sign On, Application Requests, managing workflows by providing approvals, and performing Cymmetri administrative actions (if the delegator has the required permissions on the platform), among other actions. However, the login flow for the delegatee stays the same.

Configuring the delegation on your tenant

Access the Delegation administration panel, by clicking on the Configuration left-hand side menu item and then clicking on the Delegations menu item.

For any user to be able to delegate their work to other users, the user should be added to the delegation users list; To Add Users to the delegation list so that they can delegate their activities, click on the Assign New button and select one or more users to add to this list.

User and Assignee Consent

The User and Assignee Consent sections allow organizations to align task delegation practices with their unique policies. This customizable feature empowers administrators to define specific consent texts, ensuring that both the user delegating a task and the delegatee receiving it acknowledge and agree to these terms.

The user consent will be displayed whenever the delegator (user) goes to their settings in their Workspace and assigns a delegation to an end-user (delegatee). This consent will be recorded in the Cymmetri backend for audit logging purposes.

Similarly, the assignee consent will be recorded when the end-user (delegatee/assignee) logs into the account for their manager (delegator/user).

Here's how it works:

  1. Administrator Configuration: Administrators can craft consent texts tailored to their organization's requirements. These texts typically outline the responsibilities, expectations, and any legal or compliance aspects associated with task delegation.

  2. User Perspective: When a user decides to delegate a task to someone else, they will be presented with the customized consent text. The user must carefully review and accept the terms before proceeding with the delegation process. This step ensures that the user is aware of the implications of task delegation and is willing to proceed.

  3. Assignee Perspective: On the other side, the delegatee who is about to receive the delegated task will also be presented with relevant consent text. They must thoroughly read and accept these terms before taking on the responsibility. This step helps establish clarity and accountability for the delegatee.

Suspended Users

The admin can delete the user from the users tab in the identity hub section.

After the user is deleted, the user is moved to the suspended users tab.

In the section for suspended users, the administrator has two options: they can choose to

  • Resume User - Which relocates the user back to the all users section OR

  • Force Delete - This transfers the user to the archived users section where retention of the user is not possible

Archived Users

This section stores and manages user accounts that have been archived or deactivated. These accounts are usually no longer active but are retained for historical or compliance purposes.

Accepting Delegation

Upon receiving a delegation request, the user is notified via email and within the platform.

To view the delegated task the delegatee can go to Settings->Delegation to Me to see details about the delegated tasks and the user who has assigned the task

The user needs to click on the Accept button to accept the delegation. On clicking the Accept button an Assignee(delegatee) Consent is shown which the users need to read and confirm. The Consent also shows details of the delegator and the duration of the delegation.

Once the user accepts the delegation the user sees a login button, to login into cymmetri as the delegator

On clicking the login button the delegatee is redirected to the delegator's My Workspace Dashboard.

The delegatee can access and perform actions on all the applications assigned to them and if any application is excluded during delegation they are not visible to the delegatee.

Introduction

Cymmetri's Internal Identity Provider (IDP) is a powerful authentication solution that supports seamless integration with various Identity Providers (IDPs).

We will explore the configuration options for three types of IDPs:

  • Cymmetri,

  • Active Directory, and

  • LDAP.

The flexibility of the Cymmetri Internal IDP allows you to manage multiple IDPs of the same type, making it easy to adapt to diverse environments with different Active Directory/ LDAP instances. Cymmetri's Internal IDP aims to provide a centralized and adaptable authentication solution for your environment, supporting various IDP types.

To access Internal Identity Providers navigate to Authentication-> Identity Provider->Internal IDP

To customize the applicability of different IDPs, administrators need to configure Authentication Rules. These rules enable the configuration of various conditions. When these conditions are met, the corresponding authentication mechanism or IDP is used for user authentication.

Internal Identity Provider Configuration: Cymmetri

To access Internal Identity Providers navigate to Authentication-> Identity Provider->Internal IDP.

Since Cymmetri is a default Internal IDP no configuration is needed for it. An administrator may still have an option to disable Cymmetri Authentication which can be done by editing the Cymmetri Authentication Internal IDP mechanism.

An administrator may also change the Display Name and/ or Description as shown in the screen above.

Internal Identity Provider Configuration: Active Directory

Active Directory (AD) is a robust Identity Provider (IDP) in enterprise environments. It authenticates and authorizes users, facilitating seamless access to resources. AD centralizes user management, streamlining security protocols and ensuring efficient user provisioning.

Active Directory can be utilized in Cymmetri as an Identity Provider (IDP), leveraging existing AD user accounts to access Cymmetri, as the platform supports the LDAP protocol.

For configuring AD as an Identity Provider, the primary service needed is the Adapter Service.

The Adapter Service

The Adapter Service or Auth Adapter Service is exposed as a rest service that runs on HTTPS and acts as an adapter to facilitate authentication using the LDAP protocol which is often employed for authentication purposes in various systems and every adapter service instance is called by the secret generated while installation/configuration of adapter service.

The rest endpoints are called by cymmetri-cloud AuthenticationService to connect to On-Prem AD/Ldap or cloud AD/Ldap. The AdaptorService is used to test connections, authenticate, change, and reset the password of a user.

Configuration

For configuring Active Directory as an internal IDP navigate to Authentication -> Identity Provider -> Internal IDP. Here you may either configure the already created AD Authentication instance or +Add New.

In either case, a screen opens where you need to provide the below-mentioned details.

  • Name: AD Authentication

  • IDP Type: Active Directory

  • Description: A general description of the IDP type

  • Status: Active

  • Adapter Service Domain: Location (IP) of the server on which the Adapter Service is deployed

  • Adapter Service Secret: The secret generated while installing/configuring of adapter service

  • Base DN: Active Directory root domain name

  • Search Scope: A search scope for locating users in Active Directory

Once all the details are entered Save the changes and Test the Connection using the Test Connection button.

Once the rule is configured, whenever a user matches the rule conditions, their credentials are verified against those stored in the Active Directory. Upon successful verification, the user is granted access to log in to Cymmetri.

All Users Session

All Users Session

This page provides Cymmetri administrators with the capability to monitor and manage all user sessions across the entire platform.

This functionality allows administrators to gain insights into ongoing user activities, view active sessions, and, if necessary, terminate or manage these sessions for security, compliance, or administrative purposes.

The admin can terminate all the user sessions at once or select them individually. The page also has a search option for the admin to search the desired user session.

Introduction

Cymmetri's External Identity Provider (IdP) feature allows you to authenticate user identities using different IdPs for various user types. This flexible configuration enables you to streamline access for both internal employees and external users, such as consultants, vendors, and their employees. In this documentation, we will guide you through the process of configuring an External IdP within Cymmetri's identity and access management system.

For internal employees, you can configure Cymmetri's Internal IdP mechanisms like Active Directory or LDAP. This allows seamless authentication for your organization's employees.

Whereas external users, such as consultants, vendors, and their employees, can be verified using popular External IdPs like Google, Azure, Salesforce, or any other supported IdP. This approach simplifies access for external parties while maintaining security and control.

Configuring External Identity Providers

To configure an External IdP in Cymmetri, the administrator needs to provide the following information:

  1. Name: A descriptive name for the External IdP configuration.

  2. IDP Type: The type or provider of the IdP (e.g., Google, Azure, Salesforce).

  3. Entity ID: The unique identifier for the IdP entity.

  4. SSO Service URL: The URL where Single Sign-On (SSO) requests should be sent.

  5. Destination: The location where authentication responses should be directed.

  6. Protocol Binding: The protocol used for communication with the IdP (e.g., HTTP Post, HTTP Redirect).

  7. Name ID Policy and Value: This policy defines the format and content of the identifier that represents the authenticated user. For example:

    • Policy: email

    • Value: email

  8. Certificate: The certificate used for secure communication between Cymmetri and the External IdP.

In the upcoming sections we will learn step-by-step implementation of the various External IDP mechanisms:

Google:

Google serves as a robust external Identity Provider (IDP) through its Identity Platform. Leveraging various authentication mechanisms, it facilitates secure user authentication for Cymmetri. This allows users to sign in with their Google credentials, ensuring a seamless and familiar login experience. Google's IDP mechanism is adopted for its reliability and user-friendly authentication processes, thus making it a preferred choice for integration into Cymmetri as an External IDP.

Azure Active Directory (Azure AD):

Azure AD serves as a robust external IDP, facilitating secure access into Cymmetri. Employing industry standards like OAuth 2.0 and SAML, it enables Single Sign-On (SSO) and multi-factor authentication. Azure AD seamlessly integrates with Cymmetri providing easy identity management and ensuring compliance with modern security standards.

Salesforce:

Salesforce as an external Identity Provider (IDP) offers robust authentication and access control solutions. Utilizing industry-standard protocols like SAML and OAuth, Salesforce IDP ensures secure Single Sign-On (SSO) experiences.

Configuring External Identity Providers in Cymmetri gives you the flexibility to authenticate user identities using different IdPs tailored to specific user types. Whether it's for internal employees or external collaborators, Cymmetri's External IdP feature ensures secure and convenient access to your organization's resources.

External Identity Provider Configuration - Google IDP

Google Configuration:

  1. Log in to your Google admin account and go to the Admin Section as shown below:

Once in the admin section click on Apps > Overview

In the overview page click on the Web and mobile apps tile to add a new custom app

On the Web and mobile apps page click on the Add app dropdown and then select Add custom SAML app to add the Cymmetri tenant as a custom app

Provide a relevant App Name, Optionally a description for the application can be provided. An App Icon can also be attached if required. Once entered click on the Continue button

Once the IDP metadata and certificate are obtained the Service Provider(i.e. Cymmetri) details need to be provided. We need to provide the ACS URL and the Entity ID these details can be obtained from Cymmetri as shown here. No change needs to be done for the Name ID format and Name ID, it can be kept to UNSPECIFIED and Basic Information > Primary email. Once done click on Continue

Attributes can be added on this screen which could then be sent as a SAML response to Cymmetri. These values can be used to create a user in Cymmetri if JIT provisioning is enabled on Cymmetri's side

Group membership information can also be sent by configuring groups here and if the user belongs to the configured group. Once attributes and groups are configured click on FINISH.

Once you click on the FINISH button the below screen appears that shows the configuration details. It also shows various shortcuts to Test SAML Login, Download Metadata, Edit Details, and Delete the App

Download IDP Certificate

If the administrator does not download the certificate while configuring the custom application, it can be later downloaded. For the same the administrator needs to go to Security>Authentication>SSO with SAML applications. This will open the Security Settings page from where either the IDP details like SSO URL and Entity ID can be copied and the IDP Certificate can be downloaded. These details can be used to configure the IDP in Cymmetri.

Cymmetri Configuration

Once Google IDP is configured, the administrator must proceed with the configuration on the Cymmetri side. To achieve this, the administrator needs to set up Cymmetri as a Service Provider and also incorporate Google as an external IDP.

Once the Service Provider is configured, we need to configure Google as an external IDP.

Administrator needs to go to Authentication->Identity Provider->External IDP. Here you may either configure the already created google-idp instance or +Add New

In either cases a screen opens where you need to provide the below mentioned details

  • Name: Google IdP

  • IDP Type: Google

  • Entity ID: https://accounts.google.com/o/saml2?idpid=xxxxxxxxxxxx

  • SSO Service URL: https://accounts.google.com/o/saml2/idp?idpid=xxxxxxxxxxxx

  • Destination: https://<hostname>/spsamlsrvc/samlSP/SingleSignOn

  • Protocol Binding: HTTP Post (can also be set to HTTP Redirect if it is set so in Google IDP)

  • Name ID Policy:

    • Policy: Email (This may change based on what is configured in Google IDP)

    • Value: Email (This may change based on what is configured in Google IDP)

  • Certificate: Certificate downloaded from Google IDP

  • Logout Request URL: Need to mention the SingleLogoutService url from the metadata file if SLO (Single Logout) is configured in Google.

  • Logout Protocol Binding:HTTP Post (can also be set to HTTP Redirect if it is set so in Google IDP)

  • Service Provider Id: cymmetri (Need to the select the configured Service Provider as shown above)

Once all the details are entered Save the changes.

Once the rule is configured whenever a user matches with the rule conditions the user is redirected to Google screen and the user needs to provide his/her Google credentials to be able to login into Cymmetri.

Internal Identity Provider Configuration: LDAP

Lightweight Directory Access Protocol (LDAP) serves as an important Identity Provider (IDP) in enterprise environments. It authenticates and authorizes users, facilitating seamless access to resources. LDAP is commonly used as a directory service for managing user identities and authentication information within an organization.

LDAP can be utilized in Cymmetri as an Identity Provider (IDP), leveraging existing user accounts to access Cymmetri, as the platform supports the LDAP protocol.

For configuring LDAP as an Identity Provider one of the primary services needed is the Adapter Service.

The Adapter Service

The Adapter Service or Auth Adapter Service is exposed as a rest service that runs on HTTPS acts as an adapter to facilitate authentication using the LDAP protocol which is often employed for authentication purposes in various systems and every adapter service instance is called by the secret generated while installation/configuration of adapter service.

The rest endpoints are called by cymmetri-cloud AuthenticationService to connect to On-Prem AD/Ldap or cloud AD/Ldap. The AdaptorService is used to test connections, authenticate, change, and reset the password of a user.

Configuration

For configuring Active Directory as an internal IDP navigate to Authentication -> Identity Provider -> Internal IDP. Here you may either configure the already created LDAP Authentication instance or +Add New

In either case, a screen opens where you need to provide the below-mentioned details

  • Name: LDAP Authentication

  • IDP Type: Open LDAP

  • Description: A general description of the IDP type

  • Status: Active

  • Adapter Service Domain: Location (IP) of the server on which the Adapter Service is deployed

  • Adapter Service Secret: The secret generated while installing/configuring of adapter service

  • Base DN: LDAP root domain name

  • Search Scope: A search scope for locating users in LDAP

Once all the details are entered Save the changes and Test the Connection using the Test Connection button.

Once the rule is configured, whenever a user matches the rule conditions, their credentials are verified against those stored in LDAP. Upon successful verification, the user is granted access to log in to Cymmetri.

External Identity Provider Configuration - Azure IDP

Setting up Cymmetri Service Provider for External Identity Provider Configuration

Navigate to External IDP in Identity Provider.

Select Azure-IDP.

Configure Azure AD for Creating Identity provider configuration

Now Login to the Azure portal and select Azure Active Directory.

Navigate to Enterprise applications and select New Application.

Create your own application and enter the name of the application.

Set up Single Sign On after creating the application using SAML.

Click on Edit basic SAML configuration.

Add Identifier (Entity ID) and Assertion Consumer Service URL from the XML file downloaded in step 3 (For Azure, Sign on and ACS URL are the same) and save the configuration.

Download the Certificate (Base64) from SAML Certificates.

Continue configuration of Identity Provider In Cymmetri Administration Console

Copy Azure AD Identifier from Set up, navigate to azure-idp in Cymmetri, and paste it in Entity ID. Similarly, copy the login URL and paste it into the Single Sign On Service URL in Cymmetri.

Open the Base64 certificate downloaded in step 12, copy it, and then paste it into the x509Certifcate field in Cymmetri.

Select the created service provider in the Service Provider Id field dropdown and save the changes.

Assigning Users

Assigning users to applications in Azure Administration Console to allow users to use Azure as an External Identity provider

Navigate to Enterprise applications and select the application you created in step 8.

Go to Users and Groups, and select Add user/group and add the user.

Configuring JIT provisioning in Cymmetri Administration Console

If JIT provisioning needs to be enabled for Azure AD as external Identity provider, we may set it up using the steps below.

Navigate to JIT in external identity provider and enable JIT Configuration.

The following fields are mandatory in Cymmetri - firstName, lastName, login, userType, displayName, and email.

For Azure JIT configuration, the following mapping needs to be done -

  1. First Name -

    1. Application Field - http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname

    2. Cymmetri Field - firstName

  2. Last Name -

    1. Application Field - http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname

    2. Cymmetri Field - lastName

  3. Login (Username) -

    1. Application Field - http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name

    2. Cymmetri Field - login

  4. User Type -

    1. Application Field - any string

    2. Cymmetri Field - userType

    3. Default Value - <will be one of Employee, Vendor, Consultant>

  5. Display Name -

    1. Application Field - http://schemas.microsoft.com/identity/claims/displayname

    2. Cymmetri Field - displayName

  6. Email Address -

    1. Application Field - http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name

    2. Cymmetri Field - email

In Azure Administration Console

Login to cymmetri using Azure Email Address

The user will be redirected to the Azure portal to enter the Azure credentials.

Once the credentials have been entered properly in the Azure portal, the user will be redirected back to Cymmetri and will be logged in successfully.

For any user to be able to delegate their work to other users, the user should be added to the delegation users list; Check how to Add Users to the delegation list so that they can delegate their activities.

Note: My Delegations menu will appear only if the logged-in user is added to the delegation users list. is how to Add Users to the delegation list.

You can see the other condition when the users are moved to archived users

For enabling Active Directory to be used as an IDP for a specific set of users an Authentication Rule needs to be configured. you can see the steps on how to configure Authentication Rules.

On the Google Identity Provider Detail page download the metadata file by clicking on the DOWNLOAD METADATA button. This metadata file needs to be used to get Entity ID, SSO URL, and Certificate. Administrators can download the certificate here or later as shown . Once downloaded click on Continue.

The page shows how to configure a Service Provider.

For enabling Google IDP to be used as an IDP for specific set of users an Authentication Rule needs to be configured. you can see the steps on how to configure Authentication Rules.

For enabling Open LDAP to be used as an IDP for a specific set of users an Authentication Rule needs to be configured. you can see the steps on how to configure Authentication Rules.

The page shows how to configure a Service Provider.

Replace the text "<host-name>" as the URL of the Cymmetri deployment (e.g., ) "aktestidp.ux.cymmetri.in" in the destination field - "https://<hostName>/spsamlsrvc/samlSP/SingleSignOnService" as "spsamlsrvc/samlSP/SingleSignOnService".

For enabling Azure IDP to be used as an IDP for a specific set of users an Authentication Rule needs to be configured. you can see the steps on how to configure Authentication Rules.

here
Here
Here
here.
here
Here
Here
here
https://aktestidp.ux.cymmetri.in
https://aktestidp.ux.cymmetri.in/
Here
here

Application Management

Support for Application Management

In this section, we will provide you with detailed information about the types of applications and connectors supported by Cymmetri

Supported Pre-configured Applications

Cloud Based Applications

Cymmetri seamlessly integrates with various cloud-based applications to help you efficiently manage user access and entitlements. The following are the pre-configured cloud-based applications that Cymmetri supports:

  1. Azure: Manage user access and entitlements within your Microsoft Azure environment effortlessly.

  2. Google Workplace: Simplify access management for Google Workspace applications, including Gmail, Google Drive, and more.

  3. ServiceNow: Effectively control access to your ServiceNow instance to enhance security and compliance.

  4. Salesforce: Streamline Salesforce user access management for better control and auditing.

  5. SCIM v2.0 (Salesforce): Utilize the System for Cross-domain Identity Management (SCIM) 2.0 protocol specifically for Salesforce integration.

  6. Github (Using SCIM 2.0 connector): Manage user access to GitHub repositories efficiently through our SCIM 2.0 connector.

On-Premises Applications

Cymmetri extends its support beyond cloud-based applications to include various on-premises applications. Here are the on-premises applications supported by Cymmetri:

  1. Active Directory: Efficiently manage user access to your Windows Active Directory resources.

  2. OpenLDAP: Simplify access control for your LDAP directory services with Cymmetri's integration.

  3. Lotus Notes: Streamline user access management for Lotus Notes applications.

  4. Powershell: Integrate and manage access to PowerShell scripts and resources seamlessly.

  5. CSV Directory: Effectively manage user access within CSV-based directory services.

Supported Connectors

Cymmetri offers versatile connector support to ensure seamless integration with a wide range of applications. Here are the supported connectors categorized by deployment type:

Using Cloud Connector

Cymmetri's Cloud Connectors are designed to simplify access management for various cloud-based applications. Supported cloud connectors include:

  1. Azure: Easily manage access to Microsoft Azure resources with our cloud connector.

  2. Google Workplace: Streamline access management for Google Workspace applications using our cloud connector.

  3. ServiceNow: Control access to your ServiceNow instance efficiently with our cloud connector.

  4. Salesforce: Seamlessly manage user access to Salesforce through our cloud connector.

  5. SCIM 1.1: Leverage the SCIM 1.1 protocol for connector support, ensuring compatibility with various cloud services.

  6. SCIM 2.0 (Basic, Bearer, Fixed Bearer): Our platform supports multiple SCIM 2.0 authentication methods to accommodate diverse integration needs.

Using Locally Deployed Connector

For on-premises applications and custom integration scenarios, Cymmetri offers locally deployed connectors, providing flexibility and control. Supported locally deployed connectors include:

  1. Active Directory: Manage access to Windows Active Directory resources seamlessly using our connector.

  2. Custom Script for Databases: Custom Script based connectors using groovy scripts for database applications, tailored to your specific requirements.

  3. LDAP: Integrate and manage access to LDAP-based directory services through our connector.

  4. Lotus Notes: Simplify user access management for Lotus Notes applications with our connector.

  5. Powershell: Seamlessly integrate and manage access to PowerShell resources using our connector.

  6. REST API: Extend your integration capabilities with Cymmetri's support for RESTful API connectors leveraging the flexibility of Groovy and UI based scripts.

Cymmetri's comprehensive support for both pre-configured applications and versatile connectors ensures that you have the tools needed to efficiently manage user access and entitlements across a diverse range of applications and environments. For detailed setup instructions and configuration guidelines, please refer to the specific documentation for each application and connector.

Attribute Setting

In Cymmetri, the Attribute Setting is a tool for user attribute management.

It provides administrators with granular control over attribute visibility during user creation or updation processes. This feature empowers administrators to enable or disable both predefined and custom attributes effortlessly.

When an attribute is disabled, that associated field doesn't appear anywhere in the user creation or updation pages, streamlining the user management experience.

Authentication Rules

Within Cymmetri, the authentication process is highly customizable through the definition of authentication rules. While the platform provides a default authentication rule, administrators have the ability to define custom authentication rules that align with the specific business needs and the variety of identity providers at their disposal.

For instance, let's consider a scenario where an organization has distinct user types, such as regular employees, contractors, and administrators. The administrators might require to authenticate employees with Active Directory as the identity provider and use Cymmetri's own authentication engine to verify the identity of vendors and contractors. With Cymmetri's flexibility, administrators can create authentication rules that cater to these varying requirements, ensuring a tailored and secure authentication experience based on user roles and organizational needs.

Admins can find authentication rules in Authentication tab in Cymmetri.

To create a new authentication rule, admin must simply click on the "Add New" button on the top right corner of the page.

The admin must fill in the following details

  1. The name of the rule

  2. Identity provider radio button ( Enable for External IDP or Disable for Internal IDP)

  3. Identity provider

  4. Description of the rule

  5. Active Radio Button

Conditions

The administrator has the capability to establish rules based on conditions like: Department, designation, User Type, country, and Login Pattern.

Subsequently, the administrator defines regular expressions for conditions, specifying whether they should be equal to, not equal to, and assigns corresponding values.

Cymmetri facilitates the creation of multiple conditions for an authentication rule and provides the option to group these conditions using AND or OR logic.

In the image presented above, an exemplar authentication rule is showcased. This rule is structured to authenticate a user in Cymmetri through Active Directory if two conditions are met: the user's department must be equal to "Compliance," and the user type should be "Employee."

Similarly If you wish to set the Identity provider for users having email address ending with "@cymmetri.com" then you may select condition as LoginPattern > Regular Expression and its value as (.)*(@cymmetri.com)+$; and save the details.

This demonstrates how authentication rules can be precisely configured to suit specific criteria and streamline the authentication process based on defined conditions.

Service Provider

Configuring Cymmetri as a Service Provider

Administrator needs to go to Authentication->Service Provider

Then click on +Add New button, On the screen that appears most of the data is prefilled. Yet if the administrator needs the data can be changed as per need. Once done click on Save. The prepopulated data appears as below:

Once saved the Service Provider(Cymmetri) appears as below:

The service provider is created at this step, download the metadata(xml file) of the same.

External Identity Provider Configuration - Salesforce IDP

Here below the same steps are demonstrated to use Salesforce as an Identity Provider and Cymmetri as a Service Provider.

Configuring Salesforce

For configuring Salesforce to be used as an IDP the Salesforce Administrator needs to login to Salesforce as shown below:

Once logged in the administrator needs to click on Setup on the top right and then in the search bar on the right side search for Identity Providers. Once found click on Security Controls -> Identity Provider menu

When the Identity Provider page opens click on the Enable Identity Provider button to enable Salesforce as an Identity Provider so that it can be used for authentication in Cymmetri.

When the Enable Identity Provider button is clicked it opens a page that asks you to choose a certificate. Select the default certificate here and click Save.

When saved it shows a warning message as below just click the OK button and continue.

Once confirmed the screen as shown below appears you may download the certificate and the metadata file here using the Download Certificate and Download Metadata buttons. These files can be downloaded later during the end of the process which can be seen later in the documentation below.

The metadata file appears as below, this data is used later to configure the External IDP in Cymmetri.

The certificate file appears as below this is also needed when configuring the External IDP in Cymmetri.

Once the files are downloaded next to add the Service Provider the salesforce administrator needs to click on Service Providers are now created via Connected Apps. Click here link. The mentioned link allows to create a Connected App for Cymmetri which acts as a service provider in Salesforce.

The link above leads to the page below where a new connected app can be added. The following details need to be mentioned to add a connected app:

  • Connected App Name: App Name (Cymmetri in this case)

  • API Name: Auto-populated based on the Connected App Name field, can be changed

  • Contact Email: a valid contact email

Note: Other fields shown in the image below are optional and hence can be skipped.

Next on the same page, there is a section called Web App Settings here click on Enable SAML to enable the SAML settings. Once enabled all the below-mentioned details need to be provided.

  • Entity Id: A unique identifier for a SAML entity, such as a Service Provider (SP) or Identity Provider (IDP), within a federated authentication environment.

  • ACS URL (Assertion Consumer Service URL): The endpoint where a service provider expects to receive SAML assertions from an identity provider, facilitating single sign-on (SSO) in a federated system.

  • Enable Single Logout: A configuration option indicating whether the system supports single logout functionality, allowing users to log out of all connected services in a federated environment with one action.

  • Single Logout URL: The endpoint to which a SAML entity sends logout requests as part of the single logout process when a user logs out of the federated system.

  • Single Logout Binding: The protocol or method used to transmit single logout requests and responses between SAML entities, often specified as either HTTP Redirect or HTTP POST.

  • Subject Type: Specifies the type of subject identifier used in SAML assertions, such as transient, persistent, or bearer, indicating how the identity of the user is communicated between the identity provider and the service provider.

  • Name ID Format: Defines the format of the NameID element in SAML assertions, determining how the user's identity is represented, such as email address, X.509 certificate, or unspecified.

  • Issuer: Identifies the entity that issues a SAML assertion, typically the identity provider, and is included in the SAML assertion to establish trust between the entities in a federated system.

  • IDP Certificate: The public key certificate associated with the identity provider, used by the service provider to verify the authenticity and integrity of SAML assertions and messages.

  • Signing Algorithm for SAML Messages: Specifies the cryptographic algorithm used to sign SAML messages, ensuring the integrity and authenticity of the information exchanged between identity providers and service providers in a federated

The above-mentioned details can be obtained by adding a service provider in Cymmetri as shown below. To know more about how to add a service provider in Cymmetri click here. Once created these details can be used in Salesforce as shown above.

Once all details are successfully added and saved the screen below appears which shows the configuration details.

Administrators can click on the Manage button (as shown above) to view SAML Service Provider Settings and SAML Login Information. Administrators can also download metadata files here.

The downloaded metadata file appears as below. The details mentioned in the metadata file are used to configure an External IDP in Cymmetri.

Based on the diverse profiles of users in Salesforce, the administrator needs to enable Connected App Access for these profiles. Here in this example access has been enabled for the System Administrator; similarly, it should be enabled for all profiles of various users who are intended to access Cymmetri.

For enabling the connected app administrator needs to go to Setup->Manage Users-> Profiles, then select the profile for which the connected app needs to be enabled

Once the profile is selected click on the Edit button and look for the Connected App Access section.

In the Connected App Access section look for the custom app you created(Cymmetri in this case) and click the checkbox to enable the access.

Once all the configurations on the Salesforce end are done, the administrator must proceed with the configuration on the Cymmetri side. To achieve this, the administrator needs to go to Authentication->Identity Provider->External IDP. Here you may either configure the already created salesforce-idp instance or +Add New

In either case, a screen opens where you need to provide the below-mentioned details

  • Name: salesforce-idp

  • IDP Type: Salesforce

  • Entity ID: Need to mention the EntityID from the metadata file downloaded from Salesforce

  • SSO Service URL: Need to mention the SingleSignonService URL from the metadata file downloaded from Salesforce

  • Destination: https://<hostname>/spsamlsrvc/samlSP/SingleSignOn

  • Protocol Binding: HTTP Post (can also be set to HTTP Redirect if it is set so in Salesforce)

  • Name ID Policy:

    • Policy: Unspecified(This may change based on what is configured in Salesforce)

    • Value: Login(This may change based on what is configured in Salesforce)

  • Certificate: Certificate downloaded from Salesforce

  • Logout Request URL: Need to mention the SingleLogoutService URL from the metadata file downloaded from Salesforce

  • Logout Protocol Binding: HTTP Post (can also be set to HTTP Redirect if it is set so in Salesforce)

  • Service Provider Id: cymmetri (Need to the select the configured Service Provider as shown above)

Once the external IDP is configured next we need to configure Authentication Rules as explained here and as shown below. Conditions mentioned here may vary based on actual scenario in which the IDP needs to be applicable.

Now the user can login into Cymmetri using Salesforce. The user needs to provide his/her username and click on Next.

The user is then redirected to Salesforce login page where the user needs to enter their Salesforce credentials and click on Log in

Once the salesforce credentials are successfully validated the user is redirected to Cymmetri home page.

Audit Log

In Cymmetri, the Audit Logs serve as a vital tool to maintain transparency, accountability, and security in your identity and access setup. This feature meticulously records a detailed account of various activities, ensuring a comprehensive overview of critical events and system changes.

Cymmetri uses a high performance columnar database management system designed for online analytical processing (OLAP). Its architecture and features make it well-suited for maintaining audit logs with strong protection and tamper resistance.

Below are key capabilities that contribute to these aspects:

Protection from alteration of logs data

Audit logs are critical in any security framework as they provide a reliable trail of all activities within a system. Ensuring that these logs are tamper-proof is vital to maintaining the integrity, accountability, and transparency of the data. Cymmetri, a robust identity management platform, implements several best practices and technological safeguards to ensure that audit logs remain tamper-proof. Here’s how Cymmetri achieves this:

1. Immutable Log Storage

Cymmetri uses immutable storage for audit logs, meaning once data is written, it cannot be altered or deleted. This ensures that even privileged users or attackers cannot manipulate the logs. The immutable nature of the storage ensures that records are permanent and always available for audits.

2. Cryptographic Hashing

Each audit log entry in Cymmetri is hashed using cryptographic algorithms, such as SHA-256, before being written to the storage. Hashing creates a unique digital fingerprint of the log entry, making any changes immediately detectable. If the contents of an entry were altered in any way, the hash would no longer match, thus providing tamper-evident logs.

3. Chain-Based Logging

To add an extra layer of tamper-proofing, Cymmetri leverages chain technology for audit logs. Each log entry is chained to the previous one using cryptographic hashes. This makes it impossible to alter any individual log without breaking the entire chain. chain ensures both immutability and accountability since every change or addition to the log becomes part of a transparent, verifiable sequence.

4. Role-Based Access Control (RBAC)

Cymmetri strictly enforces role-based access controls to restrict who can view and interact with the audit logs. Only authorized personnel have the rights to access the logs, and the system records all accesses, creating an additional layer of oversight. This minimizes the risk of tampering from internal threats or misconfigurations.

5. Logging Redundancy and Backup

Cymmetri ensures that audit logs are stored in multiple secure locations using distributed databases or cloud storage. This redundancy guarantees that even if one storage instance is compromised, the logs in other locations remain intact. Regular backups further protect the integrity of logs by ensuring that a historical record is always available.

6. Time-Stamping

Each audit log entry is time-stamped with a high degree of precision to ensure traceability and integrity. The timestamps are included in the cryptographic hashes, making it impossible to modify both the content and the timing of the log entries. This creates a reliable chain of events that can be used to track down and investigate suspicious activities.

Cymmetri’s tamper-proof audit logs combine state-of-the-art technologies like cryptographic hashing, immutable storage, and chain to ensure that the integrity of the audit trail remains intact. With features like RBAC, redundancy, time-stamping, and real- monitoring, Cymmetri offers a highly secure logging framework that prevents any unauthorized modifications, ensuring full accountability across its systems.

For administrators looking to review system-related logs in Cymmetri, the process is simple. Just head to the "Audit Logs" tab within the Logs section. Here, you'll find a wealth of information, covering everything from user logins to requests for accessing applications.

Audit References

Cymmetri Audit Log maintains all events processed via Cymmetri. The events are tracked based on per object event log as per the Cymmetri logging framework. Events that become part of the the log are-

  1. Human driven events processed by the system. Example- a Cymmetri Admin changing an application configuration.

  2. Scheduled events processed by the system. Example- Deprovisioning job to disable Cymmetri users.

  3. Events triggering associated processes as set up in the system. Example- Authentication service will verify the authentication rule to check for Passwordless or MFA based login journey.

Cymmetri goes the extra mile by capturing each and every system event, offering administrators a thorough understanding of what's happening within the platform.

For a closer look at a specific log entry, administrators can click on the eye icon next to it. This action provides a detailed response, offering insights into the exact activities that took place.

The admin can also filter the logs based on:

  1. The actor who performed the event

  2. The performed event

  3. Start and end date of the events

  4. Target and target type

  5. Status of the event - all, success, and failed

Cymmetri provides a reference view for the changes occurred during an audit event.

In essence, Cymmetri's Audit Logs empower administrators with the tools they need to keep a close eye on system activities, ensuring a secure and well-documented identity and access management environment.

Scheduler History

In Cymmetri the "Scheduler History" feature plays a crucial role in maintaining visibility and control over scheduled tasks and operations. This functionality is designed to offer administrators insights into the history of scheduled events, providing transparency, accountability, and efficient management of routine processes.

In the "Scheduler History" tab, accessible within the Logs section of Cymmetri, administrators can delve into the details of scheduled tasks, gaining insights into various aspects of the scheduler's operation. The information presented includes:

Event of the Scheduler: Specifies the type of scheduler event that took place.

  1. Event of the Scheduler: Specifies the type of scheduler event that took place.

  2. Description: Provides a brief description of the scheduled task or operation.

  3. Operation Performed on the Scheduled Period: Outlines the specific action executed during the scheduled period.

  4. Planned At: Indicates when the scheduler was initially planned or scheduled.

  5. Sub Event: Offers details about any sub-events associated with the scheduler operation.

  6. Executed At: Specifies the timestamp when the scheduler was executed.

  7. Execution Status: Highlights the status of the scheduler execution, indicating whether it was successful or encountered issues.

  8. Remarks (If Any): Includes any additional remarks or notes related to the scheduler operation, offering insights into the execution process.

Failed Jobs

The scheduler history provides various filters to identify status of failed jobs as shown below:

Reconciliation History

Reconciliation History provides a centralized dashboard for all system reconciliation jobs in one page. The relevant admin user can view the summary of all the tasks in progress, completed or aborted.

The tasks that have failed can be manually processed to run again by clicking on the retry button next to the failed history.

The Reconciliation job will also alert the specified Cymmetri user of the tasks over email. The configuration is two-fold-

  1. Global notification

  2. Specific application notification

Cymmetri includes the ability to retry failed records based on the failed event. Administrators can configure the maximum number of retry attempts and set up notifications according to these settings.

Cymmetri will send the alerts for all job status events to the specified user or email.

Import History

The "Import History" tab in Cymmetri provides a comprehensive record of all data imports, ensuring transparency and accountability in managing user and system information. This feature is designed to offer administrators insights into the history of data imports, facilitating effective tracking and auditing.

To check the import history in Cymmetri, go to the "Import History" tab within the Logs section. This area keeps track of all bulk import events, including imports for user and application assignments.

In this section, administrators can find a detailed history of import events, including:

  1. File Name: The name of the file that was imported.

  2. Status: The status of the import activity, indicating whether it was successful or if there were any issues.

  3. Import Type: Specifies the type of import, such as user or application assignment import.

  4. Created By: Shows who initiated or performed the import.

  5. Created At: Indicates the timestamp of when the import occurred.

For a closer look at the import history, administrators can click on the eye icon next to a specific record. This detailed view provides insights into the imported record statuses, including:

Created Successfully in Cymmetri: Indicates records that were successfully created within the Cymmetri system during the import.

Duplicated in the System While Importing: Highlights instances where records already existed in the system, preventing duplication during the import process.

Error Occurrence During Import with Remarks: Flags any errors that occurred during the import, accompanied by remarks detailing the nature of the issue.

Global Auth Policy

The Global Auth Policy allows to configure various user login parameters as shown below:

Auth Failed Count: The Auth Failed Count parameter signifies after how many failed login attempts will the user account be locked.

Unlock after Minutes: The Unlock after Minutes parameter signifies after how many minutes will a locked account be automatically unlocked.

Token Expiry Minutes: The Token Expiry Minutes parameter signifies after how many minutes will the session token expire.

Refresh Token Expiry Minutes: The Refresh Token Expiry Minutes parameter signifies after how many minutes will the refresh token expire.

User Session

Cymmetri allows users to have multiple sessions simulatenously i.e. they can login simulatenously from various locations and keep all the sessions alive. It also provides control to the user to revoke any specific or all the sessions

Password Filter

Introduction

The Cymmetri Architecture without the password filter utility allows for one-way synchronization of passwords from Cymmetri to managed applications like Active Directory. Active Directory passwords may therefore be updated, once the user password is updated in Cymmetri.

However, to keep both the Cymmetri database and Active Directory user passwords in synchronization, there is a need for Cymmetri database to receive password change notification from the Active Directory, when the password is directly updated in Active Directory.

Active Directory provides for the use of Password Filter which can intercept the request for password change and can make an API call to Cymmetri to update the password in Cymmetri database as well.

Flow Diagram

Flow Description

  1. Cymmetri Password Filter dll will be deployed in the Active directory environment and system variables (environment variables) are configured to allow the password filter to connect to the Cymmetri deployment.

  2. Active Directory server needs to be restarted once the configuration is performed.

  3. Once the user changes the password on a domain-connected computer using Ctrl+Alt+Delete utility OR if the Active Directory administrator resets the user's password using Active Directory tools, the password filter will be triggered.

  4. The password filter DLL will receive the username and the plaintext password from the Active Directory, once the password change has been applied on the Active Directory.

  5. The password filter DLL will encrypt the password using RSA encryption with a public key and will send the encrypted password and the username to the Cymmetri deployment using a REST API call over HTTPS.

  6. The Cymmetri deployment receives the username and encrypted password, it decrypts the password using private key.

  7. Once the password is decrypted, the Cymmetri deployment updates the password in Cymmetri database for the given user.

  8. If the user is assigned multiple applications for provisioning, the action of updating user's password in Cymmetri database will trigger password update for the user in other provisioned applications. However, Active directory application will not receive this password update, to avoid loops.

Configuration

Steps for deploying Password Filter DLL

  1. Download the dll file and the public key file from here - CPFv308.dll - https://drive.google.com/file/d/15uPQYnJr7HUWnxHLPSpYtsWGKkm5HnLC/view?usp=share_link public.pem - https://drive.google.com/file/d/1OdBLal4RTA5bMqABJEq3zQeLxNzSOE0R/view?usp=share_link

  2. Place the CPFv308.dll file in the C:\Windows\System32 folder.

  3. Run regedit and go to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

  4. You must now see a page similar to this:

  5. Select the element Notification Packages and double click it

  6. Add the line “CPFv308” and Click on OK to save the registry entry.

  7. Exit the registry editor.

  8. Save the public.pem file to any directory and note the name of the directory. Ex - C:\Users\Administrator\Desktop\public.pem

  9. For testing the deployment, Login into the Cymmetri portal as an administrator and note the application ID of the Active Directory application configured for provisioning. Ex - 69125912519fb123

  10. Also, create a new API client.

  1. Click on renew secret and note the bearer token generated.

Ex - eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJOZXcgQVBJIENsaWVudCIsInRlbmFudCI6IjI3NyJ9.L_q7I4MFcZSFXetdSvzD7hxvfcSrUUaJEkwhUTfHgus

  1. Go to Control Panel > System > Advanced System Settings and click on environment variables.

  2. Add the following System variables.

    1. Key = CYMMETRI_APP_ID; Value = <application-id-of-active-directory>; Example = 6015991fdfeab12c

    2. Key = CYMMETRI_CLIENT_TOKEN; Value = Authorization Bearer <token-from-api-client>; Example = Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJOZXcgQVBJIENsaWVudCIsInRlbmFudCI6IjI3NyJ9.L_q7I4MFcZSFXetdSvzD7hxvfcSrUUaJEkwhUTfHgus

    3. Key = CYMMETRI_PUBLIC_KEY_FILE; Value = <path of public.pem file>; Example = C:\Users\Administrator\Desktop\public.pem

  3. Save the environment variables.

  4. Create a folder as C:\passfilter_logs to store the logs.

  5. Take a restart of the Active Directory Server.

Configuring Password Filter in Cymmetri

  1. Navigate to the Configuration Menu.

  2. Look for the Password Filter option in the Configuration Menu.

  3. Once on the page click on "+Add New" button

  4. This will open the configuration page, You should find a toggle button to enable the Password Filter. Turn it on to enable the filter.

  5. Once the Password Filter is enabled, you'll need to choose the filter type.There are two options: "Include" and "Exclude."

    1. "Include" means that only the applications selected in the included applications dropdown will receive synced passwords and have their passwords changed correspondingly.

    2. "Exclude" means that all applications except the ones selected in the excluded applications dropdown will receive synced passwords and have their passwords changed correspondingly.

  6. Next you select the Filtered Application this is usually the managed application where the password changed has happened which in this case is Active Directory

  7. Next, determine which type of authenticator you want to use for password synchronization.

    • You typically have three options: Cymmetri Authenticator, AD (Active Directory) Authenticator, or LDAP (Lightweight Directory Access Protocol) Authenticator.

    • Choose the appropriate authenticator based on your requirements and configuration.

  8. After completing the above steps, make sure to save your configuration settings.Click on the "Save" button to save your changes.

Application Detail

The Application Detail Page provides comprehensive management features for applications within the system. It includes various sub-pages for configuring assignments, sign-on protocols, policies, provisioning settings, roles, and more. Below we outline the functionalities and configurations available on each sub-page.

Assignments

This page allows administrators to assign users and groups to an application. Users or group members can access the application if it is configured for Single Sign-On (SSO) or get provisioned in the application if it is a provisioning application.

  • Features:

    • Assign users and groups to the application.

    • View and manage existing assignments.

SignOn

Configures the application for sign-on using various protocols.

  • Supported Protocols:

    • SAML: Configure SAML-based single sign-on.

    • OpenID: Set up OpenID Connect for authentication.

    • Reverse Proxy: Configure reverse proxy settings for sign-on.

    • API SSO: Set up API-based single sign-on.

  • Features:

    • Protocol selection and configuration.

    • Test and validate sign-on settings.

    • Manage sign-on settings for different environments.

SignOn Policy

Configure Multi-Factor Authentication (MFA) for the application’s SSO settings.

  • Features:

    • Configure MFA prompts and policies.

    • Manage MFA settings to ensure secure access.

Provisioning

Configure application provisioning with various settings organized into tabs.

  • Tabs:

    • User Configuration: Define application attributes and settings for provisioning.

    • Server Configuration: Set up connector server parameters.

    • Operations: View provisioning operations supported

    • Hook Configurations: Configure hooks for triggering provisioning actions.

  • Features:

    • Manage and configure provisioning details.

    • View and edit provisioning settings.

    • Monitor provisioning operations.

Roles

Create and manage application roles and import roles from CSV files.

  • Features:

    • Create new roles.

    • Import roles via CSV for bulk role creation.

    • Manage and edit existing roles.

    • Ensure roles are correctly provisioned in target applications.

Policy Map

Configure mapping between the provisioning source application and Cymmetri user fields.

  • Features:

    • Define and manage field mappings for data synchronization.

    • View data mappings for User Pull Reconciliation.

    • Ensure accurate data exchange between systems.

Settings

Configure general settings for the application. This section allows you to modify application label and description. You may also configure other settings as shown below:

Application Risk Level:

This section lets you set application's risk which enables for identifying overall risks for users. The Risk level can be set to High, Medium, Low and Unknown

Visibility settings:

Administrator may configure visibility settings as shown below

  • Show to User: This setting when enabled lets the user see an application assigned to them.

  • User can request: This setting when enabled lets the user to request an application which is not assigned to the user.

Role settings:

Administrator may configure various role settings as shown below:

  • Multiple role assignments: which allows a user to have multiple roles in the said application and

  • Mandatory roles: This setting mandates that when the application is assigned atleast one role is assigned to the user

  • Add notes for end users and administrators.

Policy Attribute

This page lets you configure all the attributes from the provisioning source whose data needs to be synced on either sides.

Reconciliation

Configure reconciliation settings for data synchronization.

  • Features:

    • Set up pull reconciliations to retrieve data from the source application.

    • Configure push reconciliations to update data in the source application.

    • Manage reconciliation schedules and tasks.

Forms

Configure dynamic forms used in workflows for additional data collection.

  • Features:

    • Create and manage dynamic forms.

    • Configure forms to collect data during workflow processes.

    • View and edit form data as required by administrators and users

Tags & Meta

Manage tags and meta information for applications.

  • Features:

    • Create and assign tags for categorization and search.

    • Add and manage meta information for various purposes.

    • Use tags and meta data to enhance application organization, search and categorization

360 Degree Recon

  • Description: Provides a comprehensive reconciliation view for data synchronization across the system.

  • Features:

    • View detailed reconciliation data and statuses.

    • Analyze and resolve reconciliation issues.

Assigning Applications to End Users

Once the managed application has been added to your Cymmetri Identity platform tenant, you will be able to assign applications to your end-users.

Application Assignment

There are three ways in which applications can be assigned to users:

  1. Admin may assign an application directly to a user.

  2. Admin may map an application to a group; and the user is added to the group or is already part of the group.

  3. End User may request an application and is granted access to the application.

  4. Bulk Assignment of application to a set of users

Let us understand the flow for each of the above mentioned scenarios:

1. Admin assigns an application directly to the end user

Users with admin roles such as Organization Admin, Domain Admin, or Application Admin on the Cymmetri platform can assign managed applications to end-users .

  • First, we need to add the application to the Cymmetri platform

  • Next, we move to configure the application to assign it to an end user.

  • Click on the application tile to configure it.

The flow for assignment goes as follows -

Description:

  1. Admin clicks on the application tile, and starts the configuration.

  2. Click on the Assignments tab on the left hand side menu.

  3. Click on the “Assign New” button on the Users menu.

  4. Here we need to decide whether we want to provide a Lifetime Access or a Time Based Access

    1. Lifetime Access: Users have access to the application without any time restrictions.

    2. Time Based Access: Users have access to the application only for the specified range of time. We need to provide a Start Date & Time and an End Date & Time for Time Based Access.

  5. Now click on Save to register a request for the application assignment. If no Workflow is configured for the said application the application is immediately assigned to the user.

  6. If a workflow for application provisioning is configured then the workflow is been initiated.

  7. The workflow approver will then receive a request to approve the user assignment in their inbox.

  8. Now the approver may approve or reject the user assignment

  9. The approver may change the start and end date, if required; refer to the dynamic form attributes passed during the application assignment.

  10. To continue the flow click on Accept button.

  11. Now the next level of approver will be able to see the previous levels of approval, and similar to the previous level of approval, the approver may change the start and end date, if required; refer to the dynamic form attributes passed during the application assignment.

  12. Click “Accept” to proceed.

  13. After the last level approver has also approved the assignment, the backend processes will run the application provisioning flow.

  14. Once the user has been provisioned in the application, they will be able to see it in their list of applications.

2. Admin assigns an application directly to a group

Users with admin roles, such as Organization Admin, Domain Admin, or Application Admin, in a Cymmetri Identity platform deployment, will have the ability to assign entire groups of users to managed applications.

  1. First, we need to add the application to the Cymmetri platform

  2. Next, we move to configure the application to assign it to a group.

  3. Click on the application tile to configure it.

The flow for assigning a group to an application goes as follows:

Description:

  1. Click on the application tile, and start the configuration.

  2. Click on the Assignments tab on the left hand side menu.

3. Click on the “Assign New” button in the Groups section.

4. Search for the group you wish to assign the application to and click on the assign button.

5. Checking for the users who belong to the group, we can see that the application has been assigned.

6. Viewing the application tiles, we can see if the user was directly assigned the application or received access by the virtue of being part of a group.

3. User requests for an application

Users on the Cymmetri platform can request access to a managed applications as a Self-Service feature.

The flow for an end-user to request for an application is as follows:

Description:

  1. Visit the “My Workspace” menu.

  2. Click on the “My Access” left-hand side menu.

3. Now Click on the “+ Request” button on the top-right button.

  1. Here we need to decide whether we want to provide a Lifetime Access or a Time Based Access

    1. Lifetime Access: Users have access to the application without any time restrictions.

    2. Time Based Access: Users have access to the application only for the specified range of time. We need to provide a Start Date & Time and an End Date & Time for Time Based Access.

  2. Now click on Save to register a request for the application assignment. If no Workflow is configured for the said application the application is immediately assigned to the user.

  3. If a workflow for application provisioning is configured then the workflow is been initiated.

  4. The workflow approver will then receive a request to approve the user assignment in their inbox.

  5. Now the approver may approve or reject the user assignment

  6. The approver may change the start and end date, if required; refer to the dynamic form attributes passed during the application assignment.

  7. To continue the flow click on Accept button.

  8. Now the next level of approver will be able to see the previous levels of approval, and similar to the previous level of approval, the approver may change the start and end date, if required; refer to the dynamic form attributes passed during the application assignment.

  9. Click “Accept” to proceed.

  10. After the last level approver has also approved the assignment, the backend processes will run the application provisioning flow.

  11. Once the user has been provisioned in the application, they will be able to see it in their list of applications.

4. Bulk Assignment of application to a set of users

An administrator can bulk assign an application to a set of users. This an be achieved by uploading a .csv file which contains user information like., loginId, appUserId and roleId. For bulk assigning applications to users in Cymmetri platform administrator needs to

  1. Click on Identity Hub > Applications menu and then click on the Applications Assignments button.

  1. A screen pops up that lets you select the csv file you want to upload that contains the list of users to whom the application needs to be assigned, Upload the csv file, you may also use the sample data file available and modify it to match your user details.

  1. Click on the Upload File button and select the file you wish to import

  1. Once the file is selected ensure that the default parameters select match your requirement else you may change these parameters as per your requirement.

  2. Once you have ensured the parameters are correct next select the application that needs to be assigned and click on Next button.

  1. Match the Column names from the CSV file with the corresponding attributes using this File Info dialog box and click on the Import button.

Note: The "Link Application" check box is available to provision the user in the target application

  1. Once Imported results of successfully Imported Users, Duplicate Users or any error that occurred during import can be see in Logs > Import History page

  1. If any workflow is configured on the application provisioning then the corresponding workflow is triggered after the successful completeion of assignment as shown below:

Note: The link below shows steps as suggested by Salesforce to configure Salesforce as an Identity Provider:

These failed jobs are sent out as alerts to specified users as per the

Key
Value

Key = CYMMETRI_ENDPOINT_URL; Value = <domain>/apiext/api/password/filter/updateUserPassword; Example =

Search for a user in the search text box, and once the user is found, click on the “Assign” button.

4. Click on the Application Icon to start the request process

https://help.salesforce.com/s/articleView?id=sf.sso_sfdc_idp_saml_parent.htm&type=5

CYMMETRI_APP_ID

<application-id-of-active-directory-in-Cymmetri>

CYMMETRI_CLIENT_TOKEN

Authorization: Bearer <token-from-api-client>

CYMMETRI_ENDPOINT_URL

https://<cymmetri-domain>/apiext/api/password/filter/updateUserPassword

CYMMETRI_PUBLIC_KEY_FILE

<path of public key file in Active Directory Server>

Introduction to Application Management

Understand how to add and manage your cloud and on-premise applications through your Cymmetri Identity platform deployment. Your Cymmetri Identity deployment allows you to manage your cloud-based applications and on-premise applications from a single administration console.

Adding Applications

Understand how to add the applications used by your organization, to be managed your Cymmetri Identity platform deployment. Use the FAQ to learn how to add applications to be managed in the deployment.

Single Sign On

Single Sign On is the process of ensuring that once an end user is logged onto the Cymmetri Identity platform, they should be able to seamlessly move their session to any of your applications managed by your Cymmetri Identity platform deployment. Use the FAQ to learn how to configure Single Sign On for your application.

Managing the Application Sign On Policy

Modern IAM deployments wishing to have progressive authentication may require some critical application integrations within your deployment to perform additional authentication while performing Single Sign On for the end user. Use the FAQ to learn how to configure the Application Sign On Policy.

Provisioning

Provisioning refers to the process of creating, modifying, and in general pushing the user account information stored on the Cymmetri Identity platform to the applications managed by your Cymmetri Identity platform deployment. Use the FAQ to learn how to configure User Account Provisioning.

Reconciliation

Reconciliation of User accounts is a primary activity in Identity Governance, which allows for synchronisation between the user account information on the managed application and the Cymmetri Identity platform deployments, including provisioning, modifying, deprovisioning, and modifying user account attributes based on various synchronisation states. Use the FAQ to learn how to configure the Identity Reconciliation Process.

Assigning Application

Once an application has been added to the Cymmetri Identity platform deployment and the necessary configurations for Single Sign On, Provisioning and Reconciliation have been performed, an application may be assigned to an individual user or to a group of users. Use the FAQ to learn how to assign application to a user.

Provisioning How to

notifications template
https://277.newqa.cymmetri.in/apiext/api/password/filter/updateUserPassword

Cymmetri Connector List

Below is a list of Cymmetri connectors along with brief descriptions:

Dynamic Forms

Dynamic Forms enable administrators to request additional fields from either administrators or end-users when assigning applications. These additional user fields are then collected and used for provisioning the user into the managed application.

Creating a dynamic form:

For creating a dynamic form the administrator needs to configure the managed application. For e.g. Identity Hub->Applications->Service Now(Application may change )->Forms

Load the default form by clicking on the “Load Sample Data” button

Edit the default form in the JSON Schema section, In the JSON Schema section the administrator can define the form structure with the type of element, and its various properties like type, title, default value etc., a preview of the form is shown on the right hand side.

Let us create a simple form that can capture

  1. “Preferred Username” [text field] and

  2. “Request Additional Modules” [Radio] with two options “Administrator” and “Read Only”.

The code below shows how to create a simple form described above:

{ 
  "type": "object", 
  "required": [ 
    "preferredName" 
  ], 
  "properties": { 
    "preferredName": { 
    "type": "string", 
    "title": "Preferred Username", 
    "default": "" 
  }, 
  "additionalModules": { 
    "type": "string", 
    "title": "Additional Modules", 
    "enum": [ 
      "admin", 
      "readonly" 
    ], 
    "enumNames": [
       "Administrator",
       "Read-Only" 
    ], 
    "default": "" 
    } 
  }
}

The UI Schema is like a set of json properties that are used to configure how the form should look and behave. It lets you tweak things like the length of a text box or whether a choice should be shown as radio buttons or checkboxes. In the example code, we're using the UI Schema to make the "preferredName" field have a placeholder and also set a maximum length. For "additionalModules," we're using widget property to make it show up as a radio button.

{
  "preferredName": {
    "placeholder": "Enter preferred name",
    "maxLength":5
  },
  "additionalModules": {
    "ui:widget": "radio"
  }
}

The Preview Form Data displays how the data entered in the UI will be gathered and shows the structure in which the data will be sent to the API.

The preview of the form looks as below after making the changes:

Once configured the administrator can Click on the Save button.

Once saved a confirm box appears to enable the form; the administrator needs to click on the Confirm button in the popup to enable the form for the application.

Form Options

There are four options in that can be configured after enabling forms in Cymmetri

  1. Form View: If enabled, the user has the option to see the application request form within the My Access section.

  2. Form Edit: If enabled, the user has the option to edit the application request form within the My Access section, this will make changes in the respective fields in the target application.

  3. Role Assignment: If activated, the user will be displayed the request form for applications that are already assigned to them when attempting to request additional roles.

  4. Role Unassignment: If activated, the user will be displayed the form for applications when he/she is raising requests for role removal.

Adding Applications to be managed by Cymmetri

Accessing the Applications Menu

Applications menu in the administration page displays the various options pertaining to the Application Management Process.

Applications menu can be accessed as mentioned below:

Identity Hub

  1. Login as either an Organization Administrator, Domain Administrator, or Application Administrator.

  2. Click on the Identity Hub icon on the left side bar.

  3. Click on the Applications text on the slide out bar.

Understanding the applications supported by Cymmetri

Applications supported by the Cymmetri platform fall majorly into three categories -

  1. Pre-configured Applications These are the applications that have already been configured by the Cymmetri platform for provisioning on cloud or on-premises.

  2. Custom Applications for Provisioning These are the applications that you wish to manage through Cymmetri and support the generic connectors that the Cymmetri platform provides.

  3. Custom Applications for Single SignOn only When you need to add an application for the sole purpose of enabling Single Sign-On (SSO), Cymmetri offers the capability to add a custom application that can be configured for SSO using the supported mechanisms.

Adding Application

Once you have chosen the application to be added from the above categories, you are ready to add a new application.

1. Click on the “Add New” button on the top-right corner in the Applications page.

2. In the Add New Application screen, you may search for your desired application (e.g., Active Directory or some authorative source like Darwin Box or Oracle HCM), or your desired connector (e.g., REST) or choose the “Custom” application type from the available application catalogue.

And also support for other standard categories of applications as shown below:

3. Now click on the tile shown in the list below to open the right slide out menu for renaming application as shown below.

4. Add your custom label (if you wish) in the text box and click on the “Add Application” button.

Conclusion

Application has been successfully added to your listing now. You may click on the configure now button to start configuring the application.

360 Degree Recon

The 360 Degree Recon is one of a type feature of Cymmetri that enables administrators to have a holistic view of user data.

The 360-degree reconciliation process in Cymmetri is designed to ensure that identity data across different systems is consistent and up-to-date. The reconciliation process involves comparing records from Cymmetri with the records in target systems (like Active Directory) and identifying discrepancies that need to be addressed.

The 360-degree reconciliation process in Cymmetri is crucial for maintaining data integrity across all connected systems. By regularly running reconciliation, organizations can ensure that their identity data is accurate.

Configuring 360 Degree Recon

The 360 degree recon can be configured for all the provisioning applications supported by Cymmetri. Here we will be seeing an example of 360 Degree Recon with Active Directory.

Once the pull recon is configured the user next needs to go on the 360 Degree Recon page as shown below:

The 360-Degree Reconciliation page displays all the pull reconciliations configured for either users or groups. The administrator can select a configured reconciliation and run a 360-degree reconciliation for that specific pull.

Once the 360-degree reconciliation is started the administrator can then go to the History tab and view the results of the reconciliation on the reconciliation dashboard

Reconciliation Dashboard

The reconciliation dashboard provides an overview of the latest reconciliation run, including key metrics and visualizations to help administrators quickly identify and address issues.

Key Metrics:

  • Last Start Date: Indicates the start time of the most recent reconciliation run.

  • Last End Date: Indicates the end time of the most recent reconciliation run.

  • Total Processed Records: The total number of records processed during the reconciliation.

  • Records Pulled from Target App: The number of records pulled from the target application (e.g., Active Directory).

  • Present in Cymmetri only: Number of records that exist in Cymmetri but not in the target system.

  • Present in Target only: Number of records that exist in the target system but not in Cymmetri.

  • Accounts Overdue in the target: Number of accounts that are overdue in the target system but not reflected in Cymmetri.

Break Type Analysis

The break type analysis section uses a pie chart to categorize the types of breaks (discrepancies) identified during the reconciliation. In the example shown in the image, all breaks are categorized as "Present in Cymmetri only," indicating that certain records exist in Cymmetri but are missing from the target system.

Filter Options

Administrators can filter the results based on several criteria:

  • Login ID: Search for discrepancies related to specific user logins.

  • Break Type: Filter the results based on the type of break (e.g., "IDM exists, Target not exists").

  • Break Count Min/Max: Filter based on the minimum and maximum break counts.

Reconciliation Results Table

The results table provides detailed information on the discrepancies found during the reconciliation process.

Columns:

  • User Login: The login ID of the user in the Cymmetri IDM system.

  • Source Application Login: The corresponding login ID in the source application (e.g., Active Directory).

  • Application Login: The login ID in the application (if applicable).

  • Break Type: Describes the nature of the discrepancy (e.g., "IDM exists, Target not exists").

  • Break Count: Indicates how many times this particular break type was found for the user.

  • Actions: Provides option for viewing the user details for further understanding of the user data

Common Break Types

  • IDM Exists, Target Not Exists: This indicates that the user or identity exists in the Cymmetri IDM system but does not exist in the target system (e.g., Active Directory).

  • Target Exists, IDM Not Exists: This indicates that the user or identity exists in the target system but does not exist in the Cymmetri IDM system.

Actions to Resolve Discrepancies

Once discrepancies are identified, administrators can take the following actions:

  • Manual Review: Examine the discrepancy details and determine if the record should be updated, deleted, or if the discrepancy can be ignored.

  • Automated Actions: Depending on the configuration, some discrepancies can be automatically resolved by provisioning or de-provisioning the necessary accounts.

Assignment Flow 1

As the first step for configuring 360 Recon the administrator needs to configure a pull recon as explained .

Supported Provisioning Operations

Cymmetri provides a robust suite of provisioning operations that enable seamless identity and access management across various applications. Below is a detailed overview of the provisioning operations supported by Cymmetri.

1. Test Operation

  • Purpose: The Test Operation is used to validate the connectivity and configuration settings between Cymmetri and the target application or directory service. This operation ensures that all necessary parameters, such as API endpoints, credentials, and schema mappings, are correctly configured.

  • Usage Scenario: Before initiating any provisioning tasks, administrators can use the Test Operation to verify that the integration between Cymmetri and the target system is functioning as expected.

2. Sync Operation

  • Purpose: The Sync Operation synchronizes user and group data between Cymmetri and the connected applications. This operation ensures that the identity information in Cymmetri is in sync with the data in external systems.

  • Usage Scenario: The Sync Operation is typically scheduled to run at regular intervals or triggered manually to ensure that changes in the external system (e.g., new users, updated roles) are reflected in Cymmetri.

3. Search Operation

  • Purpose: The Search Operation allows administrators to query the target application or directory for specific users or groups. This operation is essential for identifying and managing specific identities in the external system.

  • Usage Scenario: Administrators can use the Search Operation to find users based on attributes such as username, email, or group membership, facilitating targeted management tasks like updates or deletions.

4. Create Operation

  • Purpose: The Create Operation is used to provision new user accounts or groups in the target application or directory based on the identity data maintained in Cymmetri.

  • Usage Scenario: When a new employee joins an organization, the Create Operation can be triggered to automatically provision their account in various applications, ensuring immediate access to necessary resources.

5. Update Operation

  • Purpose: The Update Operation allows administrators to modify existing user or group attributes in the target system. This operation is crucial for maintaining accurate and up-to-date identity information across systems.

  • Usage Scenario: If an employee's role changes, the Update Operation can be used to modify their access privileges or update their profile information in connected applications.

6. Delete Operation

  • Purpose: The Delete Operation is used to de-provision user accounts or groups from the target application or directory. This operation is essential for removing access when users leave the organization or no longer require certain resources.

  • Usage Scenario: Upon the termination of an employee, the Delete Operation can be triggered to remove their accounts from all connected applications, ensuring security and compliance.

7. Role Assign Operation

  • Purpose: The Role Assign Operation assigns specific roles to users in the target system, granting them access to particular resources or permissions.

  • Usage Scenario: When an employee is promoted to a managerial position, the Role Assign Operation can be used to grant them additional access rights aligned with their new responsibilities.

8. Role Unassign Operation

  • Purpose: The Role Unassign Operation removes previously assigned roles from users, revoking their access to certain resources or permissions.

  • Usage Scenario: If an employee is reassigned to a different department, the Role Unassign Operation can be utilized to revoke roles that are no longer relevant to their new position.

here

15Five

Employee engagement and performance management platform.

Active Directory

Directory service for managing users and resources in a Windows network.

Airbrake

Error tracking and performance monitoring tool.

Airtable

Collaborative database and spreadsheet tool.

Aiven

Managed cloud database services provider.

Akamai

Content delivery network (CDN) and cloud service provider.

AlertMediaCom

Communication and alerting platform for emergency situations.

AlertOps

Incident management and alerting system.

AlexisHR

Human resources management system.

Ally

Goal-setting and performance management tool.

AlphaSense

Market intelligence and research platform.

Alterdesk

IT service management and helpdesk software.

AlternativeInvestmentExchange

Platform for alternative investments.

Amadeus

Travel technology solutions provider.

Amazon AppStream

Desktop application streaming service.

Amazon AWS

Cloud computing services platform by Amazon.

Amazon AWS Redshift

Data warehousing service on Amazon AWS.

Amazon AWS SSO

Single Sign-On service by Amazon AWS.

Amazon Business

E-commerce platform for businesses.

AmazonManagedGrafanaSAML

Managed Grafana service with SAML support.

AmbientAI

AI-powered workplace safety and compliance solutions.

AMGTime

Time and attendance management software.

Anaplan

Cloud-based planning and performance management platform.

Anaqua

Intellectual property management software.

AndFrankly

Employee engagement and feedback platform.

Andromeda

Security and risk management solutions.

Anecdotes

Employee recognition and rewards platform.

AngelPoints

Employee rewards and recognition platform.

Animaker

DIY video-making platform.

Anodot

Real-time analytics and anomaly detection platform.

Anomalo

Data quality and anomaly detection tool.

AnswerHub

Enterprise Q&A platform.

Aon Hewitt

Human resources and benefits consulting services.

AperianGlobal

Talent management and recruitment solutions.

AppAegis

IT security and compliance solutions.

AppDynamicsEncrypted

Application performance management with encryption support.

AppDynamicsSSO

Single Sign-On support for AppDynamics.

Apperio

Legal spend management and analytics platform.

Appian

Business process management and automation platform.

AppianOnPrem

On-premises deployment of Appian's platform.

AppreciateHub

Employee recognition and rewards platform.

Apptio

IT financial management and optimization software.

Aprimo

Marketing operations and digital asset management platform.

AquaCloudSecurityPlatform

Cloud security management platform.

Arbitrip

Travel and expense management solution.

Arc GIS Online

Online geographic information system (GIS) service.

ArculessAML

Anti-Money Laundering compliance platform.

Area1Horizon

Security solution for email and phishing protection.

Area1Security

Advanced threat protection and security platform.

Ariba Network

Procurement and supply chain management platform.

AribaContractManagement

Contract management solutions by Ariba.

Articulate360

eLearning authoring and content creation suite.

Arxspan

Laboratory information management system (LIMS).

Asana

Work management and collaboration tool.

AskSpoke

IT support and service management platform.

AspenMesh

Service mesh solution for microservices.

Aspera

High-speed file transfer solutions.

AsperaV4

Updated version of Aspera's file transfer solutions.

AssemblaSAML

Single Sign-On (SSO) integration for Assembla.

Assembly

Employee engagement and performance management platform.

AssetBank

Digital asset management system.

AssetSonar

IT asset management and inventory system.

Atatus

Application performance monitoring and error tracking.

Atiim

Performance management and employee feedback platform.

Atipica

Talent acquisition and recruitment solutions.

Atlassian

Collaboration and productivity tools, including Jira and Confluence.

AtlassianCloud

Cloud-based solutions by Atlassian.

Attendease

Event management and planning software.

Aurion

HR and payroll management system.

Autodesk360

Cloud-based design and engineering tools.

Automox

Endpoint management and patching solution.

Auvik

Network management and monitoring solution.

AvidSecureInc

Security and compliance management services.

AvisoSAML

SAML integration for Aviso.

Avochato

Communication and messaging platform for sales teams.

Awardco

Employee recognition and rewards platform.

Axiom

Data management and analytics platform.

Axomo

IT management and automation solutions.

Axonius

Security asset management and visibility platform.

AxwayAmplify

Integration and API management platform by Axway.

Cloud computing services platform by Microsoft.

BakerHillNextGen

Loan origination and account management platform.

BambooHR

Human resources management and tracking software.

BambuSproutSocial

Social media management and marketing tools.

BanyanCommandCenter

Security and access management solution.

BasicOps

IT operations and incident management platform.

Beam

Employee engagement and performance management tool.

BeautifulAI

Presentation and slide design software.

BenchlingEnterprise

Life sciences research and data management platform.

BenefexRewardHub

Employee rewards and benefits management platform.

BenefitFocus

Benefits administration and management platform.

BenefitsolverSAML

SAML integration for Benefitsolver.

Beneplace

Employee benefits and discount programs.

Benetrac

Benefits administration and management software.

Benevity

Corporate social responsibility and employee giving platform.

BenSelect

Employee benefits selection and management tool.

Betterworks

Performance management and goal-setting platform.

BeyondTrust

Privileged access management and security solutions.

BigCenter

IT management and support platform.

BigID

Data privacy and protection platform.

BigPanda

IT operations and incident management platform.

BigTinCan

Sales enablement and content management solutions.

Birdeye

Customer experience and reputation management platform.

Birst

Business intelligence and analytics platform.

BitGlass

Cloud security and data protection platform.

BitlySAML

SAML integration for Bitly.

BitSightTech

Security ratings and risk management platform.

Biztera

IT management and service delivery platform.

Blackboard

Education technology and learning management system.

Blink

Employee communication and engagement platform.

BlissBook

Employee recognition and engagement tool.

Blissfully

SaaS management and vendor management platform.

BlocksEdit

Content management and editing tool.

BlogIn

Blog management and publishing platform.

BlueBoard

Employee recognition and rewards platform.

BlueJeans

Video conferencing and collaboration tool.

BlueOceanBrain

Employee learning and development platform.

BMCAtriumSSO

Single Sign-On integration for BMCAtrium.

BoardBookit

Board meeting and governance management tool.

BoardEffect

Board management and governance platform.

Bob

People management and HR platform.

Bonsai

Freelance management and invoicing software.

BoomiSAML

SAML integration for Boomi.

Boostr

Employee recognition and performance management tool.

BoxNet

Cloud storage and file sharing service.

Brainshark

Sales enablement and training platform.

BrainstormQuickHelp

Quick help and support tool for brainstorming.

BranchSAML

SAML integration for Branch.

BrandfolderSAML

SAML integration for Brandfolder.

BrandWorkzCom

Brand management and marketing platform.

Braze

Customer engagement and marketing automation platform.

Breezy

Recruitment and applicant tracking system.

BreezyHR

HR and recruitment software.

BridgeCrew

Cloud security and compliance platform.

BrightEdge

SEO and content performance platform.

CentrifyPrivilegeAccessService

Privileged access management and security solution.

CenturyLink

Telecommunications and cloud services provider.

CequenceSecurity

Security solutions for data and infrastructure.

Cerby

Security and compliance management platform.

Ceresa

Data protection and privacy management solution.

Ceridian

Human resources and payroll management software.

Cerner

Health information technology solutions provider.

Certify

Expense management and reporting tool.

Cezanne

HR software for small and medium-sized businesses.

CGRFoundation

Foundation for research and data management.

ChangePoint

Project and portfolio management software.

Chargebee

Subscription management and billing platform.

ChartHop

Org chart and employee directory tool.

ChartioSAML

SAML integration for Chartio.

ChatterSAML

SAML integration for Chatter.

ChatWork

Team communication and collaboration platform.

CheckpointInfinityPortal

Security management and threat detection solution.

Cherwell

IT service management and workflow automation platform.

ChorusAI

Conversation analytics and sales performance platform.

ChromeRiver

Travel and expense management software.

CSV Directory

Custom integration for CSV-based directories.

Custom

Custom integration solution for unique use cases.

DarwinBox

HR and talent management software.

FreshDesk

Customer support and ticketing system.

Freshservice

IT service management and helpdesk software.

Freshworks

Customer engagement and support platform.

Google

Google services integration, including Google Workspace.

Google Workplace

Productivity and collaboration suite by Google.

hCaptcha

CAPTCHA service for protecting websites from bots.

Hive

Collaboration and project management tool.

Ingenium

Enterprise content management system.

Jedox

Performance management and business analytics platform.

Jenkins

Continuous integration and delivery tool.

Joomla

Content management system for websites.

LDAP

Lightweight Directory Access Protocol for directory services.

Liferay

Enterprise portal and content management system.

Lotus Notes

Email and collaboration software.

Lucid

Visual collaboration and diagramming tool.

Lucidchart

Diagramming and flowchart creation software.

ManageEngine AD Manager Plus

Active Directory management and reporting tool.

ManageEngine ServiceDesk Plus

IT service management and helpdesk solution.

NetSuite

Cloud-based ERP and business management software.

NextThink

IT operations analytics and end-user experience management.

oDesk

Freelance job platform (now Upwork).

Office365

Productivity suite by Microsoft.

OracleFusion

Oracle's suite of cloud-based enterprise applications.

OracleHCM

Human Capital Management solutions by Oracle.

PagerDuty

Incident management and response platform.

Paladin

Legal and compliance management software.

PaloAltoNetworksSAML

SAML integration for Palo Alto Networks.

PAM

Privileged Access Management solutions.

Pivotal

Application development and deployment platform.

Piwik

Open-source web analytics platform (now Matomo).

PowerShell

Task automation and configuration management framework.

Prezi

Presentation software with interactive and dynamic features.

ReadCube

Research management and document discovery tool.

SailPointIIQ

Identity governance and administration platform.

Salesforce

Customer relationship management (CRM) platform.

Samanage

IT service management and asset management software.

SAPNetWeaverSAML

SAML integration for SAP NetWeaver.

ScienceLogic

IT operations and management platform.

SCIM v1.1

System for Cross-domain Identity Management version 1.1.

SCIM v2.0 (Basic)

Basic implementation of SCIM v2.0 for user management.

SCIM v2.0 (Bearer)

SCIM v2.0 with Bearer token authentication.

SCIM v2.0 (Fixed Bearer)

SCIM v2.0 with Fixed Bearer token authentication.

SCIM v2.0 (Github)

SCIM v2.0 implementation for GitHub.

SCIM v2.0 (Salesforce)

SCIM v2.0 implementation for Salesforce.

Script Connector

Custom integration using scripting for unique requirements.

ServiceNow

IT service management and enterprise workflow solutions.

Shutterstock

Stock photo and image licensing platform.

Sisense

Business intelligence and analytics platform.

Slack

Team communication and collaboration tool.

Smartsheet

Work management and automation platform.

SNOW Commander

Snowflake data management and automation tool.

Snowflake

Cloud-based data warehousing platform.

Splunk

Data analysis and monitoring platform.

SplunkCloud

Cloud-based data analysis and monitoring by Splunk.

SuccessFactors

Human resources management and talent management solutions.

SugarCRM

Customer relationship management (CRM) software.

Tableau

Data visualization and business intelligence platform.

TeamViewer

Remote access and support software.

Vimeo

Video hosting and sharing platform.

Zendesk

Customer service and support ticketing system.

Zenduty

Incident management and response platform.

ZingHR

Human resources management and payroll solutions.

Google Workspace Provisioning

Google Workspace is a software-as-a-service platform (SAAS) that provides email, calendar, documents and other services. This connector uses the Google Workspace provisioning APIs to create, add, delete and modify user accounts and email aliases.

Note: 1. Only the Premium (paid) or Educational versions of Google Workspace provide access to the provisioning APIs. 2. Connector will not work on the free Google Workspace Domain

Configuration

For Configuring Google Workspace for provisioning we need to first obtain the client_secret.json file from the Google Workspace instance.

Create New Project

And the on the NEW PROJECT link on top right

Next enter the Project name and select Organisation and Location as shown below and click on CREATE button

ADMIN SDK API:

The Admin SDK API is needed to programmatically manage and interact with various aspects of a Google Workspace domain, such as users, groups, organizational units, and settings. Here are some key reasons why the Admin SDK API is essential:

  1. User Management: The Admin SDK API allows you to create, retrieve, update, and delete user accounts in your Google Workspace domain. You can manage user details such as name, email address, password, and organizational unit.

  2. Group Management: You can create, retrieve, update, and delete groups within your Google Workspace domain using the Admin SDK API. This includes managing group members and settings.

  3. Organizational Unit Management: The API enables you to manage organizational units (OUs) within your Google Workspace domain. You can create, retrieve, update, and delete OUs, as well as move users and groups between OUs.

  4. User Reports: The Admin SDK API provides access to various reports about user activity, such as login activity, email sending/receiving activity, and more. These reports can help you monitor and analyze user behavior within your domain.

  5. Settings Management: You can manage various domain-wide settings, such as email routing, calendar sharing settings, and device management settings, using the Admin SDK API.

  6. Security and Compliance: The API provides features for managing security and compliance settings within your Google Workspace domain, such as 2-step verification, password policies, and audit logs.

To enable ADMIN SDK API click on Enabled API & Services and Search for Admin SDK API:

Click on Admin SDK API and then click on the Enable button

Once enabled, Click on CREDENTIALS tab

Now click on Credentials section and click on CREATE CREDENTIALS button and in that select OAuth client ID option

Select Desktop app as Application type, provide a name for the OAuth 2.0 client and then click on the CREATE button

A response screen is visible that shows that the "OAuth client created" It also displays Your Client ID and Your Client Secret. You may download the JSON here using the DOWNLOAD JSON option.

Click on OAuth consent screen and then Click on EDIT APP. Enter the required details and Click on SAVE AND CONTINUE button

Select Internal as User Type if you want to restrict access only to the users of your organization.

Search for Admin SDK API on the Scopes screen and select scope for user: .../auth/admin.directory.user

Select the scope for group: .../auth/admin.directory.group

Next Click on Credentials section and downlaod OAuth client json file on your local machine by clicking on the Download OAuth client button.

$ jar xvf net.tirasa.connid.bundles.googleapps-1.4.2.jar
$ java -jar net.tirasa.connid.bundles.googleapps-1.4.2.jar /path/to/client_secrets.json
Please open the following address in your browser: ?
access_type=offline ...

This command opens the default browser, and loads a screen on which you authorize consent to access the Google Apps account. When you have authorized consent, the browser returns a code. Copy and paste the code into the terminal from which you ran the original command

Attempting to open that address in the default browser now... 
Please enter code: XXXXXXXX

A response similar to the following is returned.

Once the above information is obtained we need to configure the Google Workspace in Cymmetri with Server Configuration and User Configuration as shown below:

Once the configuration is done click on TEST CONFIGURATION button to check if the configuration is working.

Once the test is successful next go to the Assigments section and assign the application to a user as shown below:

Once assigned ensure that the user is created in Google Workspace.

LDAP Provisioning

Integration with LDAP

  1. For LDAP connector integration we need an LDAP server with the following detail sample.

    Host/IP

    LDAP Base Context

    service user (Manager Username)

    password (Manager User password)

  2. After configure LDAP server we need to configure the Ldap application into the Cymmetri.

  3. Check policy map to add proper attributes as needed by LDAP schema.

Powershell Provisioning

Integration with Powershell

  1. For the powershell connector we need a windows server machine with a connId server on it.

  2. Configure powershell connector with following properties

  3. Must configure powershell script with valid data using the reference below

Azure Provisioning

Azure provisioning in Cymmetri involves setting up configurations to automate the creation and management of user accounts in Microsoft Entra ID. This allows for seamless user onboarding and offboarding processes.

To implement Azure provisioning in Cymmetri, follow these general steps:

The administrator needs to login to Azure Portal: https://portal.azure.com

Once logged in click on More services-> button

In the next screen click on Identity -> App registrations inside the Identity management section

Next click on New registration to register a new App. Registering your application establishes a trust relationship between your app and the Microsoft identity platform. The trust is unidirectional: your app trusts the Microsoft identity platform, and not the other way around. Once created, the application object cannot be moved between different tenants.

Next enter the Application Name and select the Supported account types to organizational directory only : Accounts in this organizational directory only (Cymmetri Organization only - Single tenant) and then click on Register

Once registered next click on Authentication menu and +Add a platform.

On the next screen select Mobile and desktop applications

Enter a Custom redirect URIs: http://localhost and click on Configure

Further enable the Public Client flows and click on Save button

Next go to Certificates and secrets menu and create a new client secret:

Next enter a Description for the and select the duration after which the secret would Expire -Recommended is 180 days (6 months) but can be changed as per the need. Once both the details are entered click on Add button

Next copy and save the Client Secret ID and Client Secret Value in a safe and accessible place. Client secret values cannot be viewed, except for immediately after creation. Be sure to save the secret when created before leaving the page.

Once the client secret details are stored next click on API permissions menu and then + Add a permission

On this page select Microsoft Graph

On the next page we require permissions for both Delegated and Application permissions. Select each type of permission and in that Search and select the following permissions/scopes:

  1. APIConnectors.Read.All

  2. Directory.ReadWrite.All

  3. OpenID (Not available for Application Permissions)

  4. PrivilegedAccess.Read.AzureAD

  5. User.ReadWrite.All

  6. Directory.Read.All

Once all the permissions are added a warning is shown: "You are editing permission(s) to your application, users will have to consent even if they’ve already done so previously." The administrator needs to click on the "Grant admin consent for Cymmetri Organization" link

On the click of the link a popup appears to grant admin consent, click on Yes

Next click on Expose an API and then click on Add to add an Application ID URI: The Application ID URI, also called identifier URI, is a globally unique URI used to identify the web API. This URI is the prefix for scopes in the Oauth protocol. You can either use the default value in the form of api://, or specify a more readable URI.

On the next page keep the default values intact and click on Save button

Finally you can see the Overview page that contains all the information you need to configure Azure in Cymmetri.

Also the User config Application Authority can be obtained from the endpoint section in the Overview page:

This completes the Azure side of the configuration, next the administrator needs to need to move to Cymmetri and configure the Azure application. Mentioned below are the steps required to configure Azure in Cymmetri:

Add a new Azure application Identity Hub->Applications and then click on the +Add New button

Once added the administrator needs to go to Policy Attribute section and ensure all the below mentioned attributes are present (Add if not already present):

  • mailNickname

  • displayName

  • __PASSWORD__

  • __NAME__

  • userPrincipalName

  • givenName

  • surname

  • mail

  • usageLocation

Next the administrator needs to go to the Policy Map section and ensure a mapping shown as below is created:

Application Field
Field
User Principal
Create Only
Update Only

displayName

displayName

-

True

True

__NAME__

login

-

True

True

__PASSWORD__

password

-

True

True

mailNickname

mailNickName

-

True

True

userPrincipalName

login

True

True

True

givenName

firstName

-

True

True

surname

lastName

-

True

True

mail

email

-

True

True

usageLocation

country

True

True

azureLicense

azureLicense

<actual license key>

True

True

Once the policy map is created next the administrator needs to go to Provisioning section and then to Server Configuration and need to configure the connector server as shown below:

Once the Server Configuration is done next the administrator needs to implement User Configuration with the below mentioned fields:

  • User config Application Authority: This is the authority under which the application operates. For example, if you're using Azure AD, the application authority might be https://login.microsoftonline.com/<tenant_id>/oauth2/authorize

  • User config application client id: This is the unique identifier for your application. It is provided by Azure when you register your application. For example, e9a5a8b6-8af7-4719-9821-0deef255f68e.

  • Client Secret: This is a secret key used by the application to prove its identity when requesting access tokens. It should be kept confidential. For example, 7f7df45a-251e-49d3-a396-748bf8e05a3c.

  • User config domain: This is the domain associated with your Azure AD. For example, contoso.onmicrosoft.com.

  • User config base password: This is the base password used for your application. For example, MyBasePassword123.

  • Redirect URI: This is the URI to which Azure AD will redirect the user after authentication. For example, api://05b765c3-d64f-7704-b0d8-5c4c6bc674df

  • User config resource URI: This is the URI of the resource (API, web app, etc.) that the application wants to access. For example, https://graph.microsoft.com.

  • Azure Tenant ID: This is the identifier for your Azure AD tenant. For example, 72f988bf-86f1-41af-91ab-2d7cd011db47.

  • User config base username: This is the base username used for your application. For example, MyUsername@contoso.onmicrosoft.com.

Once the configuration is done and saved, Next click on TEST CONFIGURATION to test if Cymmetri is able to connect to Azure Server.

Assign various Product Licenses to user

For assigning any sort of licenses to a user of various products two main policy map entries need to done as shown below:

  • azureLicense: Need to provide license key for the product you wish to assign to the user

  • usageLocation: This field needs a two-letter country code (ISO standard 3166). Required for users that are assigned licenses due to legal requirements to check for availability of services in countries. Examples include: US, JP, and IN.

The value for azureLicense can be obtained as explained below:

Once you click that it opens the page from which we can copy the product id from URL as shown below:

Once all the above configuration is done, on the same page in Cymmetri go to Assignments section and assign users to the application and ensure that these users are created in Azure's Microsoft Entra ID along with the Microsoft Teams license.

Active Directory (AD) Provisioning

Pre-requisites:

Make sure you have the following information before you proceed further:

  • Cymmetri login credentials

  • Access to IIS (Internet Information Services) to install certificates.

    • Access to Windows Certificate Services

  • Active Directory Essentials:

    • Server hostname and password

    • OU (Organisation Unit) name, if any

    • SSL ports need to be enabled on your side

    • Export the CA Certificate from Active Directory and import it into the Connector Server.

    • Make sure the certificate is installed on the Connector Server

Step 1 - Configure your Active Directory Certificate and export it to Connector Server

Once the certificate has been imported per the above instructions, you must restart the application to apply the changes made.

Step 2 - Add a new Active Directory application to Cymmetri

  • Navigate to the Identity Hub on the left navigation bar and click the Applications tab. You will see a list of existing applications.

  • Click 'Add New', and you will find the entire list of all available applications.

  • Search for Active Directory on the top right and click on it. You should see the Active Directory application sidebar on the right.

  • The Application Label has a default name for the Active Directory application and can be changed according to your choice. Click 'Add Application' from the bottom right to add the Active Directory application to your Cymmetri profile.

You have now added an Active Directory application to Cymmetri.

Step 3 - Adding Policy Attributes

  • After adding the Active Directory, the 'Configure Now' button is enabled. Click this button to start setting up your Active Directory application.

  • Define which attributes should be fetched from your Active Directory. You can do that by going to the Policy Attribute section.

  • Here below are shown some Active Directory attribute descriptions

Attribute Name
Description

CN

Common Name/ Display Name

RDN

Relative Distinguished Name - An RDN is the relative portion of a Display Name (DN).

SN

Surname

Policy Attributes - Policy attributes are user attributes (field names) in the Active Directory.

  • The policy attribute table is prefilled with standard Active Directory Attributes by default. Please verify if it works for you. If not, follow the below mappings for the provisioning to work.

  1. telephoneNumber - mobile

  2. sAMAccountName - login

  3. givenName - firstName

  4. mail - email

  5. sn- lastName

  6. cn - firstName

2.1 Adding new attributes

  • If the standard list does not contain the attributes you want to include, you can add new attributes by clicking the 'Add new' button on the right.

  • Fill in the attribute name, and description and click Save.

  • Also, toggle the Active switch to enable this new attribute.

Besides the present policy attributes, you need to add a custom attribute in case you're going for group provisioning, i.e. memberOf attribute.

Step 4 - Map your Active Directory Attributes to Cymmetri

  • Now that you've defined what attributes to fetch from Active Directory, you will map these to Cymmetri user attributes.

  • On the same window, navigate to the policy map in the left navigation bar.

Policy Map - Mapping of Cymmetri and Active Directory attributes.

  • You will see that the attributes are set to False by default. Our first step in the mapping process is to enable the attributes for syncing.

  • Click on the edit button next to the 'Application Field' name.

  • The 'Application Field' indicates the Active Directory field name, and the 'Cymmetri Field' indicates the Cymmetri field name.

  • To map the attributes, we need to sync the attributes on create and update only. Hence, these checkboxes need to be checked.

  • The 'Set default value' field accepts the default value you enter here if the field is empty in Active Directory.

  • Next, click on the 'Update' button.

  • Similarly, repeat this for all attributes.

  • One exception is the sAMAccountName field. The 'Is User Principal' checkbox is enabled by default because it is the primary key (unique data) on the Active Directory side, and login is the primary key on Cymmetri side; leave it checked.

Some important policy map fields which need to be declared in the policy map are as follows.

Active Directory attribute
Cymmetri Attribute

__NAME__

Users Display Name

__PASSWORD__

Users password

sAMAccountName

Unique login attribute

cn

Unique login attribute (specific to user)

rdn

Used to pass the OU (Organization Unit) path

  • If any attribute is missing from the policy map but present in your policy attribute. Add it by clicking the 'Add Cymmetri Field' and follow the same steps to map it to the appropriate field.

  • If you want to add a new field that is not present even in Cymmetri, click on the 'Add Custom Field' button. For group provisioning, the memberOf attribute must be configured with the memberOf attribute from the custom attribute.

Hook Configuration

Every organization has its own custom implementation scenarios such as duplicate checks for login id, emails and displaynames; similarly provisioning to specific AD OUs based on various conditions. Hooks allow to transform the data and execute the validation rules as per the custom implementation scenarios.

Step 5 - Configure the Connector Server

  • The connector server is a tool that provides different connectors that enable various provisioning operations from different sources to Cymmetri. Below you may see that Cymmetri supports all the various lifecycle operations needed to seamlessly perform various user operations.

  • In our case, we will prepare the connector server to work with the Active Directory source.

  • Click Provisioning from the left navigation bar and enable application provisioning by sliding the slider button.

  • Once you enable the application provisioning, you must take care of two configurations to successfully provision Active Directory data to Cymmetri.

  1. Server Configuration - Consists of configuring the connector server.

  • Enter the IP address of the host server and its password. The rest of the fields come pre-filled with default values; you can change them according to your use case. Next, click on the save configuration button.

Field Name
Description

Host server

The IP address of the host server

Server port

Port of the host server

Server Password

Host Server password

Server connector bundle version

Version number of the connector server bundle

Server connector bundle name

Name of the connector server bundle

Server connector name

Given name of the connector server

Server Connector Timeout

Timeout of the connector server in milliseconds

Server Connector UseSSL

Connector server SSL configuration

  1. User Configuration - Consists of all user settings like domain name, search filter, etc. We can also configure an OU (Organisational Unit) in this window.

Field Name
Description

Entry object classes

Object classes to which the Account class is mapped

Root suffixes

Display names used for Active Directory synchronisation to Cymmetri, such as domain controller name

Principal password

Admin password to connect to Active Directory

Default id Attribute

Default attribute Id

Custom user search filter

Search filter used to search accounts

Connector messages

Custom connector messages

Default group container

Default group container can be used during create operation in case of entry DisplayName is not explicitly mentioned

Default people container

Default people container can be used during create operation in case of entry DisplayName is not explicitly mentioned

Group owner reference attribute

Group attribute referencing (by DisplayName) the users members of a group

Custom group search filter

User search filter for groups

Group search scope

Choose object, onlevel or subtree

Server hostname

Active Directory server hostname that would connect to Cymmetri

Conservative membership policy

Conservative management of assigned groups. The groups already assigned to an user on Active Directory will not be removed.

Memberships

Groups to identify users to synchronize. The connector ignores any changes about users not member of indicated groups.

Verify memberships in OR

Indicate if specified memberships must be verified using 'OR' logical operator.

Object classes to synchronise

User object classes to synchronise. The connector ignores any changes if it cannot find modified entry object classes in this property.

Page size

Get users from Active Directory with the provided size

Pageable result

Get users from Active Directory with the provided size pageable result

Server port

Port of the Active Directory connector server

Principal

Admin username of the Active Directory

Permit password update only

Permit password update only.

Create/delete operation will be denied, while other attributes update requests will be ignored.

Retrieve deleted groups

Indicate if deleted groups must be synchronized also.

Retrieve deleted users

Indicate if deleted users must be synchronised also.

SSL

True if the SSL certificate is configured

Trust all certs

Indicative if all server certificates can be trusted

UID attribute

Unique Identifier Attribute

Base context for user entry searches

Display the Name of OU (Organization Unit), Root domain or Root controller required for user entry search

User search scope

The scope could be a subtree or object for user search

Note - You would need to change the below fields as per your organisation:

  1. Root suffix - Add your domain name here.

  2. Principal Password - Add your server password here.

  3. Server Hostname - Add your server name here.

  4. Principal - Add your admin Display Name of the Active Directory.

  5. The base context for user search - You can add your Organisation Unit here.

  6. The base context for group search - Add the base context to enable group search

  7. Server port - Ensure that it is set to 636 for push

  8. Page size- Define pageable result count for users

  9. SSL - True is SSL is configured

  10. Trust all certs - True.

  11. Disable User OU Movement - Provide the path for disabling OU movement here.

Click on the save configuration button. Next, click on test configuration to see a successful toast message if your configuration is successful.

While configuring, you might encounter errors like:

  • Authentication exception - Failure due to incorrect username and password.

    • Solution - Keep all your necessary credentials handy and enter the details carefully

  • Socket timeout - Connection refusal by the target system

    • Solution - Please ensure your network connections are accurate to avoid socket timeout errors.

  • SSL issue - SSL issue occurs mainly if certificates are not configured correctly.

    • Solution - Follow the steps mentioned in Step 1 rigorously to import the Active Directory certificate to avoid SSL-related errors.

Step 6 - Start syncing users from Active Directory to Cymmetri

The last step of onboarding users is to add the users from Active Directory to Cymmetri by Reconciliation.

Pull Reconciliation

Pull users from your Active Directory to Cymmetri.

  • Click the 'Reconciliation' tab on the left navigation bar on the same page.

  • Next, click the 'Add New' button under the pull tab.

  • Add the field name details, and give a name to the pull reconciliation.

    • The modes field is prefilled with 'FILTERED_RECONCILIATION'; keep it as it is. It specifies the mode of Reconciliation.

    • The Sync fields are a drop-down menu with Cymmetri attributes that need to be mapped with the Source attributes, that is, your Active Directory attributes. Choose the correct mappings for these fields.

    • Keep the Status as Active.

    • Types are prefilled with the User. Keep it as it is.

  • You can define the conditions for the Pull Reconciliation. It specifies the different scenarios of the Reconciliation. All the tabs have the same options in the dropdown: IGNORE, UPDATE, DEPROVISION, PROVISION, UNLINK, LINK, ASSIGN, UNASSIGN.

Options
Usage

IGNORE

You can skip the process by choosing this option.

UPDATE

It can be used when you want to modify or reflect new changes.

PROVISION

You can use this option to onboard the users.

DEPROVISION

You can use this option to remove the users.

LINK

You can use this option to link the users to Cymmetri

UNLINK

You can use this option to unlink the users to Cymmetri

ASSIGN

You can use this option to assign the users to Cymmetri

UNASSIGN

You can use this option to unassign the users to Cymmetri

Here is an example scenario:

User exists in target system, not in Cymmetri
User exists in both systems
User does not exist in target system, but in Cymmetri
Result

UPDATE

IGNORE

PROVISION

Update user details in the target system, ignore if a user is present in both systems and provision users that do not exist in the target system.

  • The options to choose in a Reconciliation operation depend on your use case and change accordingly.

  • In this case, we have chosen to IGNORE the users that do not exist in your Active Directory but exist in Cymmetri. Also, IGNORE users who are present in both the systems. PROVISION the users that exist in your Active Directory but do not exist in Cymmetri.

  • Hit the save button on the top left and click the 'Run now' button. The status of the recon changes to active.

  • You can head to the users tab and check if users are synced. If the reconciliation is successful, the users start appearing in this tab.

Push Reconciliation

Sync your user data to Active Directory.

  • Navigate to the push tab and click on 'Add New'.

  • Repeat Steps 2 and 3 from Pull Reconciliation.

  • Move towards the Search Filter and Add Criteria section on the page.

  • Fill in all the user details like Department, Designation, User Type, Location, Manager, Group, if any, email and mobile number. Keep the account status slider in the unlocked option. Choose user status as 'Active'.

  • Set the conditions for the Push Reconciliation.

  • Click on Save at the top-right corner of the page.

  • Click on 'Run-now' to start the Push Reconciliation. You can check the status on the Reconciliation page.

  • Navigate to the users page to check the new users added to Cymmetri.

History

Navigate to the History tab to check and track the pull and push Reconciliation of the past.

Click on the eye icon to view the Push/Pull reconciliation operation.

All the details configured in the Push/Pull Reconciliation can be seen here. It also displays the Summary of Pending, Synced and Error records.

Logs

If, in any case, you're facing issues, head to the Logs->Audit Log to check for error logs.

  • Click on the eye icon to check the event attributes in the audit log for errors.

Go To and create a new Project if not already created. A new project needs to be created because it allows you to manage the credentials required to access Google APIs and services securely. A new project can be created by clicking on the New Project on top right or by clicking on the the Resource Dropdown

Next download thebundle for Google Workspace from the Connector Server website. Once downloaded open a new command prompt and change to the directory where you have downloaded the bundle and run the following command on the client_secrets.json file that you obtained earlier step:

Reference:

Go to and login using the admin credentials. Once logged in go to Billing->Licenses->Microsoft Teams Exploratory

Exporting your Active Directory certificate to the Connector Server is a necessary and crucial step. This ensures that the Active Directory and Cymmetri Identity Server can communicate over LDAPS (LDAP over SSL). For this to happen, LDAPS requires a properly formatted certificate installed in your Active Directory Domain Controllers. Please refer to this link and follow the same steps:

Azure
https://console.developers.google.com/
net.tirasa.connid.bundles.googleapps-1.4.2.jar
https://drive.google.com/drive/folders/1XHt6aNmPzs7V7OKesk31FwqLxGf3u2ST?usp=sharing
https://admin.microsoft.com/
https://www.manageengine.com/products/active-directory-audit/kb/how-to/how-to-install-ssl-certificates-in-active-directory.html
here

API Extension

Cymmetri framework to extend the out of box use cases and support custom requirements from the platform

Reference API calls

The following are the APIs calls.

Important Note:

RESTful API – Assigned application search user

Purpose: This API is used to create application hook

URL: http://<tenant_domain>/api/user/listByApplication

Method: POST

Example Request:

curl --location --request POST 'http://api.cymmetri.in/usersrvc/api/user/listByApplication' \

--header 'Content-Type: application/json' \

--header 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJhZG1pbiIsImRlbGVnYXRlZSI6bnVsbCwiZGVsZWdhdGVlSWQiOm51bGwsImZpcnN0TG9naW4iOmZhbHNlLCJyb2xlcyI6WyJPUkdfQURNSU4iLCJVU0VSIl0sInRlbmFudElkIjoiZ2s0MCIsImV4cCI6MTY0NzAxNzEwNywidXNlcklkIjoiNjE3MDE1YTNjMDQ4MTc1NmI3OThhY2EyIiwiaWF0IjoxNjQ3MDExMTA3fQ.8j711_L--eQHHfen2GPI1qWCmUWRd4n6O44HCZhuRSo' \

--data-raw '{

"keyword":"shu",

"pageNumber": "0",

"pageSize": "10",

"filter": {

"applicationId": "617253cc2fb4b2125b237b75"

},

"sortDirection": "ASC",

"sortOn": [

"id"

]

}'

Sample Response:

On success:

{

"success": true,

"data": {

"content": [

{

"id": "619ce9a69139ca14885a4717",

"displayName": "John Snow",

"firstName": "John",

"lastName": "Snow",

"email": null,

"mobile": null,

"designation": "Developer",

"status": "ACTIVE",

"profilePic": null,

"login": "john.snow",

"initialLoginPending": true,

"startDate": null,

"endDate": null,

"provStatus": {

"617253cc2fb4b2125b237b75": "SUCCESS_UPDATE"

}

}

],

"pageable": {

"sort": [

{

"direction": "ASC",

"property": "id",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": true,

"descending": false

}

],

"pageNumber": 0,

"pageSize": 10,

"offset": 0,

"paged": true,

"unpaged": false

},

"last": true,

"totalPages": 1,

"totalElements": 1,

"sort": [

{

"direction": "ASC",

"property": "id",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": true,

"descending": false

}

],

"first": true,

"number": 0,

"numberOfElements": 1,

"size": 10,

"empty": false

},

"timestamp": "02-Mar-2022 01:58:57",

"message": null,

"errorCode": null

}

On failure:

Response 1#

{

"data": null,

"success": false,

"errorCode": "PROVSRVC.APPLICATION_NOT_FOUND",

"message": null,

"timestamp": "02-Mar-2022 01:59:39"

}

RESTful API – Assigned application search group

Purpose: This API is used to get an application hook for the provided application id and type.

URL: http://<tenant_domain>/api/group/groupListByApplication

Method: POST

applicationId: Application id

Example Request:

curl --location --request POST 'http://localhost:9080/api/group/groupListByApplication' \

--header 'Tenant: gk16'

--data-raw '{

"filter": {

"applicationId": "617253cc2fb4b2125b237b75"

},

"keyword": "gold",

"pageNumber": 0,

"pageSize": 10,

"sortDirection": "ASC",

"sortOn": [

"name"

]

}'

Sample Response:

On success:

{

"success": true,

"data": {

"offset": 0,

"pageSize": 10,

"totalElements": 1,

"totalPages": 1,

"elements": [

{

"id": "621cdbb7776c95564c0313ab",

"name": "Gold",

"type": "LocalGroup",

"description": "Gold group",

"ouId": "",

"ouName": null,

"parentGroupIds": null,

"directParentGroupId": null,

"userCount": 0,

"appCount": 1

}

],

"pageNumber": 0,

"sort": {

"orders": [

{

"direction": "ASC",

"property": "name"

}

],

"sorted": true

}

},

"timestamp": "03-Mar-2022 05:29:23",

"message": null,

"errorCode": null

}

On failure:

Response 1#

{

"data": null,

"success": false,

"errorCode": "PROVSRVC.APPLICATION_NOT_FOUND",

"message": null,

"timestamp": "03-Mar-2022 05:29:49"

}

RESTful API – Application reconciliation pull filter search

Purpose: This API is used to list reconciliation pull for provided application id and keyword.

URL: https://<tenant_domain>/provsrvc/reconciliation/pull/search

Method: POST

applicationId: applicationId

keyword : keyword

Example Request:

curl --location --request POST 'https://mru18.cymmetri.in/provsrvc/reconciliation/pull/search' \

--header 'Tenant: mru18' \

--data-raw '{

"filter": {

"applicationId": "614b5d3489ad96554e89e2ab"

},

"keyword": "",

"pageNumber": 0,

"pageSize": 10,

"sortDirection": "DESC",

"sortOn": [

"updatedDateTime"

]

}'

Sample Response:

On success:

{

"success": true,

"data": {

"content": [

{

"id": "621cca3f9423002d41cbbed4",

"name": "AD-ADMIN-USERS",

"type": "USER",

"status": "ACTIVE",

"applicationId": "614b5d3489ad96554e89e2ab",

"targetSystemSearchQueryFilter": null,

"idmRepositoryField": "login",

"sourceAttributeName": "cn",

"reconType": "PULL",

"reconMode": "FILTERED_RECONCILIATION",

"reconConditions": {

"TARGET_DELETED_IDM_EXISTS": "IGNORE",

"TARGET_EXTSTS_IDM_EXISTS": "IGNORE",

"TARGET_EXTSTS_IDM_NOT_EXISTS": "PROVISION"

},

"lastRunDateTime": null,

"createdDateTime": "2022-02-28T13:12:31.07",

"updatedDateTime": "2022-03-02T12:45:31.069",

"version": 2

},

...

...

],

"pageable": {

"sort": [

{

"direction": "DESC",

"property": "updatedDateTime",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": false,

"descending": true

}

],

"pageNumber": 0,

"pageSize": 10,

"offset": 0,

"paged": true,

"unpaged": false

},

"last": true,

"totalPages": 1,

"totalElements": 3,

"first": true,

"sort": [

{

"direction": "DESC",

"property": "updatedDateTime",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": false,

"descending": true

}

],

"numberOfElements": 3,

"size": 10,

"number": 0,

"empty": false

},

"timestamp": "03-Mar-2022 08:41:03",

"message": null,

"errorCode": null

}

On failure:

Response 1#

{

"success": false,

"data": null,

"timestamp": "03-Mar-2022 09:06:43",

"message": null,

"errorCode": "INVALID_ARGUMENTS"

}

Response 2#

{

"success": false,

"data": null,

"timestamp": "03-Mar-2022 09:06:43",

"message": null,

"errorCode": "PROVSRVC.UNKNOWN"

}

RESTful API – Application reconciliation push filter search

Purpose: This API is used to list reconciliation push for provided application id and keyword.

URL: http://<tenant_domain>/reconciliation/push/search

Method: POST

applicationId: Application Id.

keyword : keyword

Example Request:

curl --location --request POST 'https://mru18.cymmetri.in/provsrvc/reconciliation/pull/search' \

--header 'Tenant: mru18' \

--data-raw '{

"filter": {

"applicationId": "614b5d3489ad96554e89e2ab"

},

"keyword": "",

"pageNumber": 0,

"pageSize": 10,

"sortDirection": "DESC",

"sortOn": [

"updatedDateTime"

]

}'

Sample Response:

On success:

{

"success": true,

"data": {

"content": [

{

"id": "62207b1655a2d10f525dc2bf",

"name": "AD-Admin",

"type": "USER",

"status": "ACTIVE",

"applicationId": "614b5d3489ad96554e89e2ab",

"idmSearchQueryFilter": {

"location": null,

"reportingManager": null,

"department": null,

"designation": null,

"group": null,

"email": null,

"mobile": null,

"status": [],

"userType": null,

"locked": false

},

"idmRepositoryField": "login",

"sourceAttributeName": "cn",

"reconType": "PUSH",

"reconMode": "FILTERED_RECONCILIATION",

"reconConditions": {

"IDM_DELETED_TARGET_EXISTS": "IGNORE",

"IDM_EXTSTS_TARGET_EXISTS": "IGNORE",

"IDM_EXTSTS_TARGET_NOT_EXISTS": "PROVISION"

},

"lastRunDateTime": null,

"createdDateTime": "2022-03-03T08:23:50.963",

"updatedDateTime": "2022-03-03T08:23:50.963",

"version": 0

}

…

…

],

"pageable": {

"sort": [

{

"direction": "DESC",

"property": "updatedDateTime",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": false,

"descending": true

}

],

"pageNumber": 0,

"pageSize": 10,

"offset": 0,

"paged": true,

"unpaged": false

},

"last": true,

"totalPages": 1,

"totalElements": 3,

"first": true,

"sort": [

{

"direction": "DESC",

"property": "updatedDateTime",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": false,

"descending": true

}

],

"numberOfElements": 3,

"size": 10,

"number": 0,

"empty": false

},

"timestamp": "03-Mar-2022 08:40:09",

"message": null,

"errorCode": null

}

On failure:

Response 1#

{

"success": false,

"data": null,

"timestamp": "03-Mar-2022 09:06:43",

"message": null,

"errorCode": "INVALID_ARGUMENTS"

}

Response 2#

{

"success": false,

"data": null,

"timestamp": "03-Mar-2022 09:06:43",

"message": null,

"errorCode": "PROVSRVC.UNKNOWN"

}

RESTful API – Application role filter search

Purpose: This API is used to list application roles with provided application id and keyword.

URL: http://<tenant_domain>/applicationRole/findAppRolesByApplicationId

Method: POST

application id: applicationId

keyword: keyword

Example Request:

curl --location --request POST 'https://mru18.cymmetri.in/provsrvc/applicationRole/findAppRolesByApplicationId' \

--header 'Tenant: mru18' \

--data-raw '{

"filter": {

"active": true,

"applicationId": "614b5d3489ad96554e89e2ab"

},

"keyword": "",

"pageNumber": 0,

"pageSize": 10,

"sortDirection": "ASC",

"sortOn": [

"id"

]

}'

Sample Response:

On success:

{

"success": true,

"data": {

"content": [

{

"id": "621f2996a36e574d3e7ab4a7",

"roleId": "ROLE_ID_101",

"roleName": "ADMIN",

"roleDescreption": "This role is for admin users.",

"applicationId": "614b5d3489ad96554e89e2ab",

"cosoType": "Admin",

"active": false,

"mappedBusinessRoles": [],

"createdDateTime": "2022-03-02T08:23:50.608",

"updatedDateTime": "2022-03-02T13:48:54.189",

"version": 3

},

...

...

],

"pageable": {

"sort": [

{

"direction": "ASC",

"property": "id",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": true,

"descending": false

}

],

"pageNumber": 0,

"pageSize": 10,

"offset": 0,

"paged": true,

"unpaged": false

},

"last": true,

"totalPages": 1,

"totalElements": 3,

"first": true,

"sort": [

{

"direction": "ASC",

"property": "id",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": true,

"descending": false

}

],

"numberOfElements": 3,

"size": 10,

"number": 0,

"empty": false

},

"timestamp": "03-Mar-2022 09:20:03",

"message": null,

"errorCode": null

}

On failure:

Response 1#

{

"success": false,

"data": null,

"timestamp": "03-Mar-2022 09:06:43",

"message": null,

"errorCode": "INVALID_ARGUMENTS"

}

Response 2#

{

"success": false,

"data": null,

"timestamp": "03-Mar-2022 09:06:43",

"message": null,

"errorCode": "PROVSRVC.UNKNOWN"

}

RESTful API – Application Policy Map filter search

Purpose: This API is used to search PolicymapTenant.

URL: http://<tenant_domain>/policyMapTenant/findAll

Method: POST

tenantApplicationId: Tenant Application Id

objectType: Mapping Object Type

internal: Internal Attribute

external: External Application Attribute

Example Request:

curl --location --request POST 'api.cymmetri.in/provsrvc/policyMapTenant/findAll' \

--data-raw '{

"keyword": "lastName",

"pageNumber": 0,

"pageSize": 10,

"filter": {

"tenantApplicationId": "61dd1da8db654e41881b5273",

"objectType": "USER"

},

"sortDirection": "DESC",

"sortOn": [

"internal"

]

}'

Sample Response:

On success:

{

"success": true,

"data": {

"content": [

{

"id": "61dd1da8db654e41881b5281",

"internal": "lastName",

"external": "sn",

"mandatory": false,

"script": null,

"createdDateTime": "2022-01-11T06:03:20.202",

"updatedDateTime": "2022-01-11T06:03:20.202",

"version": 0,

"default_val": "",

"tenant_applicationId": "61dd1da8db654e41881b5273",

"object_type": "USER",

"isCustom": false,

"scriptEnable": false

}

],

"pageable": {

"sort": [

{

"direction": "DESC",

"property": "internal",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": false,

"descending": true

}

],

"pageNumber": 0,

"pageSize": 10,

"offset": 0,

"paged": true,

"unpaged": false

},

"last": true,

"totalPages": 1,

"totalElements": 1,

"first": true,

"sort": [

{

"direction": "DESC",

"property": "internal",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": false,

"descending": true

}

],

"numberOfElements": 1,

"size": 10,

"number": 0,

"empty": false

},

"timestamp": "03-Mar-2022 07:13:09",

"message": null,

"errorCode": null

}

RESTful API – App description in selfservice application list API

Purpose: This API is used to get paginated lists with filters.

URL: https://<tenant_domain>/selfservice/api/selfservice/applications

Method: POST

Example Request:

curl --location --request POST 'https://gk40.cymmetri.in/selfservice/api/selfservice/applications' \

--header 'Connection: keep-alive' \

--header 'Pragma: no-cache' \

--header 'Cache-Control: no-cache' \

--header 'sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="96", "Google Chrome";v="96"' \

--header 'Accept: application/json' \

--header 'content-type: application/json' \

--header 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJhZG1pbiIsImRlbGVnYXRlZSI6bnVsbCwiZGVsZWdhdGVlSWQiOm51bGwsImZpcnN0TG9naW4iOmZhbHNlLCJyb2xlcyI6WyJPUkdfQURNSU4iLCJVU0VSIl0sInRlbmFudElkIjoiZ2s0MCIsImV4cCI6MTY0NzAxNDY2NywidXNlcklkIjoiNjE3MDE1YTNjMDQ4MTc1NmI3OThhY2EyIiwiaWF0IjoxNjQ3MDA4NjY3fQ.jP2BgjiOVUcdxhImVvdwy18puEylWSSOVHnWA_2hhJU' \

--header 'sec-ch-ua-mobile: ?0' \

--header 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36' \

--header 'sec-ch-ua-platform: "Linux"' \

--header 'Origin: https://gk40.cymmetri.in' \

--header 'Sec-Fetch-Site: same-origin' \

--header 'Sec-Fetch-Mode: cors' \

--header 'Sec-Fetch-Dest: empty' \

--header 'Referer: https://gk40.cymmetri.in/' \

--header 'Accept-Language: en-GB,en-US;q=0.9,en;q=0.8' \

--header 'Cookie: deviceId=6e4caedd-beaf-444c-9312-21b219bb3709; Correlation=B194B86832FB4683ABC43EA6077944E2; Correlation=1E83B306404E4E46A2F6BE7D5A79C3BC; RefreshToken=fc6b1bcc-1c00-4663-b6ef-441051fb2e57; sessionId=75bdbb27-cf85-4102-9ba7-0cc5a84f8fb4' \

--data-raw '{

"direction": "ASC",

"keyword": "",

"pageNumber": 0,

"pageSize": 16,

"sort": "NAME"

}'

Sample Response:

On success:

{

"success": true,

"data": {

"offset": 0,

"pageSize": 16,

"totalElements": 5,

"totalPages": 1,

"elements": [

{

"endDate": null,

"deprovNotification": false,

"enabled": true,

"tagLine": "Directory service developed by Microsoft",

"id": "617253cc2fb4b2125b237b75",

"name": "Active Directory",

"appUrl": "",

"icon": "iVBORw0KGgoAAAANSUhEUgAAALoAAAC6CAYAAAAZDlfxAAAACXBIWXMAAAsSAAALEgHS3X78AAAgAElEQVR4nO2dCXQU17nnv1tb.....truncated"

}

],

"pageNumber": 0,

"sort": {

"orders": [

{

"direction": "ASC",

"property": "NAME"

}

],

"sorted": true

}

},

"timestamp": "03-Mar-2022 05:41:09",

"message": null,

"errorCode": null

}

RESTful API – New Joiner List API

Purpose: This API is used to get list of selfservice dashboard new Joiner list of logged in users.

URL: http://<tenant_url>/usersrvc/api/user/getSubOrdinates

Method: POST

Example Request: Need to pass filter as createdFrom and createdTo date time difference for seven day.

curl --location --request POST 'http://api.cymmetri.in/usersrvc/api/user/getSubOrdinates' \

--header 'Content-Type: application/json' \

--header 'Tenant: gk17' \

--header 'UserId: 61e81227aa505f4393b93405' \

--data-raw '{

"filter": {

"createdFrom": "2022-01-04T10:26:56.030Z",

"createdTo": "2022-03-04T10:26:56.030Z"

},

"keyword": "",

"pageNumber": 0,

"pageSize": 10,

"sortDirection": "ASC",

"sortOn": [

"id"

]

}'

Sample Response:

On success:

{

"success": true,

"data": {

"content": [

{

"login": "nilesh",

"displayName": "Nilesh Dhepe",

"userId": "61e947c37dce7c5e40134f1f",

"profilePic": null,

"qualitativeRisk": null,

"sodViolations": null

},

{

"login": "workflow.one",

"displayName": "Test Workflow",

"userId": "61ee658de3a8361263cab0d1",

"profilePic": null,

"qualitativeRisk": null,

"sodViolations": null

},

{

"login": "workflow.two",

"displayName": "Test Workflow",

"userId": "61f7b3b50d84c22f79e1debd",

"profilePic": null,

"qualitativeRisk": null,

"sodViolations": null

},

{

"login": "mrunal",

"displayName": "Mrunal Chaple",

"userId": "61f8cda757a8e27934066a91",

"profilePic": null,

"qualitativeRisk": null,

"sodViolations": null

},

{

"login": "manoj.b",

"displayName": "Manoj Barapatre",

"userId": "61f8d81883126a511188e2ae",

"profilePic": null,

"qualitativeRisk": null,

"sodViolations": null

},

{

"login": "man.ba",

"displayName": "Manoj Bara",

"userId": "61f9160ed9800d4dbbc1baed",

"profilePic": null,

"qualitativeRisk": null,

"sodViolations": null

}

],

"pageable": {

"sort": [

{

"direction": "ASC",

"property": "id",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": true,

"descending": false

}

],

"pageNumber": 0,

"pageSize": 10,

"offset": 0,

"paged": true,

"unpaged": false

},

"last": true,

"totalElements": 6,

"totalPages": 1,

"first": true,

"number": 0,

"sort": [

{

"direction": "ASC",

"property": "id",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": true,

"descending": false

}

],

"numberOfElements": 6,

"size": 10,

"empty": false

},

"timestamp": "04-Mar-2022 10:39:22",

"message": null,

"errorCode": null

}

On failure:

Response 1#

{

"success": true,

"data": null,

"timestamp": "04-Mar-2022 10:39:22",

"message": null,

"errorCode": null

}

RESTful API – On board API - Get App incomplete config

Purpose: This API is used to get count of onboard application config incomplete.

URL: http://<tenant_url>/provsrvc/applicationTenant/getApplicationIncompleteConfig

Method: GET

Example Request:

curl --location --request GET 'http://api.cymmetri.in/provsrvc/applicationTenant/getApplicationIncompleteConfigCount' \

--header 'Tenant: gk17' \

--header 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJnazE3IiwiZGVsZWdhdGVlIjpudWxsLCJkZWxlZ2F0ZWVJZCI6bnVsbCwiZmlyc3RMb2dpbiI6ZmFsc2UsInJvbGVzIjpbIk9SR19BRE1JTiIsIlVTRVIiXSwidGVuYW50SWQiOiJnazE3IiwiZXhwIjoxNjQ2NjQ2NjQ0LCJ1c2VySWQiOiI2MWU4MTIyN2FhNTA1ZjQzOTNiOTM0MDUiLCJpYXQiOjE2NDY2NDA2NDR9.snwC7XVRWM5S-gCP53fXXObh9aROFtZDtfOXQCUDPps'

Sample Response:

On success{

"success": true,

"data": 3,

"timestamp": "07-Mar-2022 08:11:48",

"message": null,

"errorCode": null

}

On failure:

Response 1#

{

"success": true,

"data": 0,

"timestamp": "04-Mar-2022 10:39:22",

"message": null,

"errorCode": null

}

RESTful API – On board API - Get appCount, adminCount, UserCount

Purpose: This API is used to get count of application, admin and user.

URL: http://<tenant_url>/usersrvc/api/user/getOnboardCount

Method: GET

Example Request:

curl --location --request GET 'http://api.cymmetri.in/usersrvc/api/user/getOnboardCount' \

--header 'Content-Type: application/json' \

--header 'Tenant: n23' \

--header 'UserId: 6176c0b33c79f20dde6fd732' \

--header 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJnazE3IiwiZGVsZWdhdGVlIjpudWxsLCJkZWxlZ2F0ZWVJZCI6bnVsbCwiZmlyc3RMb2dpbiI6ZmFsc2UsInJvbGVzIjpbIk9SR19BRE1JTiIsIlVTRVIiXSwidGVuYW50SWQiOiJnazE3IiwiZXhwIjoxNjQ2NjQ2NjQ0LCJ1c2VySWQiOiI2MWU4MTIyN2FhNTA1ZjQzOTNiOTM0MDUiLCJpYXQiOjE2NDY2NDA2NDR9.snwC7XVRWM5S-gCP53fXXObh9aROFtZDtfOXQCUDPps'

Sample Response:

On success:

{

"success": true,

"data": {

"appCount": 9,

"adminCount": 1,

"userCount": 25

},

"timestamp": "07-Mar-2022 08:11:27",

"message": null,

"errorCode": null

}

On failure:

Response 1#

{

"success": true,

"data": {

"appCount": 0,

"adminCount": 0,

"userCount": 0

},

"timestamp": "07-Mar-2022 08:11:27",

"message": null,

"errorCode": null

}

RESTful API – System KPIs API

Purpose: This API is used to get the count of application,role,rule,workflow,password policy,active user,total user and unlogged user.

URL:https://<tenant_url>/usersrvc/api/user/getSystemKPICount

Method: GET

Example Request:

curl --location --request GET 'https://macos.cymmetri.in/usersrvc/api/user/getSystemKPICount' \

--header 'Accept: application/json' \

--header 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJhZG1pbiIsImRlbGVnYXRlZSI6bnVsbCwiZGVsZWdhdGVlSWQiOm51bGwsImZpcnN0TG9naW4iOmZhbHNlLCJyb2xlcyI6WyJPUkdfQURNSU4iLCJVU0VSIl0sInRlbmFudElkIjoibWFjb3MiLCJleHAiOjE2NDcwMDg1MjUsInVzZXJJZCI6IjYxN2Y4YmIxZDE5MDViNjcyYzQ3N2QzMiIsImlhdCI6MTY0NzAwMjUyNX0.JzhcbfcQXxZoCYH5Mi_HmRCHZf_FVIr3OYrewl7vkjc'

Sample Response:

On success:

{

"success": true,

"data": {

"appCount": 80,

"roleCount": 5,

"activeUserCount": 128,

"totalUserCount": 131,

"unloggedUserCount": 106,

"passwordPolicyCount": 2,

"workflowCount": 3,

"ruleCount": 6

},

"timestamp": "11-Mar-2022 12:42:30",

"message": null,

"errorCode": null

}

On failure:

Response 1#

{

"success": true,

"data": {

"appCount": 0,

"roleCount": 0,

"activeUserCount": 0,

"totalUserCount": 0,

"unloggedUserCount": 0,

"passwordPolicyCount": 0,

"workflowCount": 0,

"ruleCount": 0

},

"timestamp": "11-Mar-2022 12:42:30",

"message": null,

"errorCode": null

}

RESTful API – Request, Claims and My Request Count

Purpose: This API is used to get count of requests, claims and my requests.

URL: https://<tenant_url>/workflowsrvc/api/workflowtaskassignment/user/request/claims/count

Method: GET

Example Request:

curl --location --request GET 'https://gk40.cymmetri.in/workflowsrvc/api/workflowtaskassignment/user/request/claims/count' \

--header 'Tenant: gk40' \

--header 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJtcnUxOCIsImRlbGVnYXRlZSI6bnVsbCwiZGVsZWdhdGVlSWQiOm51bGwsImZpcnN0TG9naW4iOmZhbHNlLCJyb2xlcyI6WyJPUkdfQURNSU4iLCJVU0VSIl0sInRlbmFudElkIjoibXJ1MTgiLCJleHAiOjE2NDY2NzE2MTYsInVzZXJJZCI6IjYxNGI1Yjc1ODVmODU0NGYxY2RkOTcxNSIsImlhdCI6MTY0NjY2NTYxNn0.bViQdrikfQD1xdI6Waf_Sk6LOYQh-ilHVq4dMYfVt3E'

Sample Response:

On success:

{

"success": true,

"data": {

"requestCount": 12,

"clamisCount": 6,

"requestorCount": 0

},

"timestamp": "10-Mar-2022 07:07:48",

"message": null,

"errorCode": null

}

On failure:

Response 1#

{

"success": true,

"data": {

"requestCount": 0,

"clamisCount": 0,

"requestorCount": 0

},

"timestamp": "04-Mar-2022 10:39:22",

"message": null,

"errorCode": null

}

RESTful API – Applications assigned to user API search

Purpose: This API is used to search application assigned to user.

URL: https://<tenant_url>/usersrvc/api/user/listApplications

Method: POST

Example Request:

curl --location --request POST 'https://s3.cymmetri.in/usersrvc/api/user/listApplications' \

--data-raw '{

"pageNumber": 0,

"pageSize": 20,

"userId": "61d7f610dd92d761faa278f2",

"appName":"service"

}'

Sample Response:

On success:

{

"success": true,

"data": {

"offset": 0,

"pageSize": 12,

"totalElements": 1,

"totalPages": 1,

"elements": [

{

"appId": "6226051994c38e414989eccd",

"appName": "ServiceNow",

"tagLine": "Workflow Automation Platform",

"status": "",

"appType": "GROUP",

"groupId": "61dea46ef515150ebe517b0d",

"endDate": null,

"provisionEnable": true,

"assignRoles": null

}

],

"pageNumber": 0,

"sort": null

},

"timestamp": "11-Mar-2022 01:06:33",

"message": null,

"errorCode": null

}

RESTful API – List of assigned & unassigned application

Purpose: This API is used to get assigned and unassigned application.

URL: https://<tenant_url>/provsrvc/applicationTenant/applicationListByPage

Method: POST

Example Request:

curl --location --request POST 'https://s3.cymmetri.in/provsrvc/applicationTenant/applicationListByPage' \

--data-raw '{

"displayName": "",

"order": "DESC",

"pageNo": 0,

"size": 10,

"sortBy": "displayName",

"tag": "",

"userId":"61d7f610dd92d761faa278f2"

}'

Sample Response:

On success:

{

"success": true,

"data": {

"content": [

{

"id": "61dbfdf6b30690468b0d4a79",

"appName": "Google Workplace",

"icon": null,

"tagLine": "Integrated Collaboration & Productivity Apps from Google",

"status": "ACTIVE",

"provisionEnable": false,

"ssoEnable": true,

"assigned": true

},

{

"id": "61dd1da8db654e41881b5273",

"appName": "Active Directory",

"icon": null,

"tagLine": "Directory service developed by Microsoft",

"status": "ACTIVE",

"provisionEnable": true,

"ssoEnable": false,

"assigned": true

},

{

"id": "6225f81edd7111640e094f8d",

"appName": "Google Workplace5",

"icon": null,

"tagLine": "Integrated Collaboration & Productivity Apps from Google",

"status": "ACTIVE",

"provisionEnable": true,

"ssoEnable": false,

"assigned": true

}

],

"pageable": {

"sort": [

{

"direction": "DESC",

"property": "displayName",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": false,

"descending": true

}

],

"pageNumber": 0,

"pageSize": 10,

"offset": 0,

"paged": true,

"unpaged": false

},

"totalPages": 2,

"totalElements": 12,

"last": false,

"first": true,

"sort": [

{

"direction": "DESC",

"property": "displayName",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": false,

"descending": true

}

],

"numberOfElements": 10,

"size": 10,

"number": 0,

"empty": false

},

"timestamp": "11-Mar-2022 02:10:38",

"message": null,

"errorCode": null

}

RESTful API – Application Access expiring new API

Purpose: This API is used to get list of application of user with there expiry days

URL: https://<tenant_url>/selfservice/api/selfservice/applicationswithexpiry

Method: POST

Example Request:

curl --location --request POST 'https://as100.cymmetri.in/selfservice/api/selfservice/applicationswithexpiry' \ --header 'Connection: keep-alive' \ --header 'Pragma: no-cache' \ --header 'Cache-Control: no-cache' \ --header 'sec-ch-ua: "Google Chrome";v="93", " Not;A Brand";v="99", "Chromium";v="93"' \ --header 'Accept: application/json' \ --header 'content-type: application/json' \ --header 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJhZG1pbiIsImRlbGVnYXRlZSI6bnVsbCwiZGVsZWdhdGVlSWQiOm51bGwsImZpcnN0TG9naW4iOmZhbHNlLCJyb2xlcyI6WyJPUkdfQURNSU4iLCJVU0VSIl0sInRlbmFudElkIjoiYXMxMDAiLCJleHAiOjE2NDcwMDk4NzgsInVzZXJJZCI6IjYyMTRkYjdiZDY2MWE1NzM4NmE3MWYxMCIsImlhdCI6MTY0NzAwMzg3OH0.LKZci0Yqeoyn4RHUIyYBFq7O5ATeDuCerZ0QdJ243gY' \ --header 'sec-ch-ua-mobile: ?0' \ --header 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.63 Safari/537.36' \ --header 'sec-ch-ua-platform: "Linux"' \ --header 'Origin: https://as100.cymmetri.in' \ --header 'Sec-Fetch-Site: same-origin' \ --header 'Sec-Fetch-Mode: cors' \ --header 'Sec-Fetch-Dest: empty' \ --header 'Referer: https://as100.cymmetri.in/' \ --header 'Accept-Language: en-GB,en-US;q=0.9,en;q=0.8' \ --header 'Cookie: deviceId=48ba110c-c93c-45ac-92dc-3c6e04e74473; app_73e5c5f8-276b-47bb-a6a5-b6f82a779d79=e689a8da-faa7-46f5-9c7a-2800abdd206a; Correlation=C43A4277E7AB46178F0000BE4DD72F0C; RefreshToken=1ac7eea6-28a6-4bb8-997f-d7381a3dd7d1; sessionId=3417319f-789a-4849-8faa-bf180f4bec14; device=cf7bbf2a-161c-11ec-b3ec-39287c680726' \ --data-raw '{ "keyword": "", "pageNumber": 0, "pageSize": 10, "filter": {}, "sortDirection": "DESC", "sortOn": [ "plannedStart" ] }'

Sample Response:

On success:

{

"success": true,

"data": {

"offset": 0,

"pageSize": 10,

"totalElements": 3,

"totalPages": 1,

"elements": [

{

"id": "62220c747dab08061e00ba7b",

"name": "Active Directory",

"icon": "iVBORw0KGgoAAAANSUhEUgAAALoAAAC6CAYAAAAZDlfxAAAACXBIWXMAAAsSAAALEgHS3X78AAAgAElEQVR4nO2dCXQU17nnv1tb71q7BUJIzW7Jxo5N6zlOsPD2COBlEsnbiZFf,

"period": 20,

"tagLine": "Directory service developed by Microsoft"

},

{

"id": "62260e904f6c552b8b489c20",

"name": "Google Workplace",

"icon": "iVBORw0KGgoAAAANSUhEUgAAALoAAAC6CAIAAACWbMCmAAAACXBIWXMAAAsSAAALEgHS3X78AAAgAElEQVR4nO2dd3wURf/Ht1xLcnfpvUB6uRRSKFKl9w6C+KgPj2B57D6gD/o8iOVBEaQIiCiIgoBKNSAgVXoPISG910u5S0+u7/xed3vZ27vsXW6T4A+fZ97/ZLM7uzs7+9mZ73xn5nsoAACBQOwDg+UEsR8oFwgLoFwgLIBygbAAygXCAigXCAugXCAsgHKBsADKBcICKBcIC6BcICyAcoGwAMoFwgIoFwgLoFwgLIBygbAAygXCAigXCAugXCAsgHKBsADKBcICKBcIC6BcICyAcoGwAMoFwgIoFwgLoFwgLIBygbAAygXCAigXCAugXCAsgHKBsADKBcICKBcIC6BcICyAcoGwAMoFwgIoFwgLoFwgLIBygbAAygXYQGUC4QFUC4QFkC5QFgA5QKxFwRB/g+Z9ki2AOTkrgAAAABJRU5ErkJggg==",

"period": 5,

"tagLine": "Integrated Collaboration & Productivity Apps from Google"

},

{

"id": "62260e994f6c552b8b489c28",

"name": "PowerShell",

"icon": "iVBORw0KGgoAAAANSUhEUgAAALoAAAC6CAYAAAAZDlfxAT/gAAAABJRU5ErkJggg==",

"period": 4,

"tagLine": "Command-line Shell from Microsoft"

}

],

"pageNumber": 0,

"sort": {

"orders": [

{

"direction": "DESC",

"property": "plannedStart"

}

],

"sorted": true

}

},

"timestamp": "11-Mar-2022 01:42:30",

"message": null,

"errorCode": null

}

RESTful API – Password Policy - maximum (optional)- minimum (required) password length

Purpose: This API is used to validate password against password policy

URL: https://<tenant_url>/authsrvc/passwordPolicy/pub/validate

Method: POST

Example Request:

curl 'https://as100.cymmetri.in/authsrvc/passwordPolicy/pub/validate' \

-H 'Connection: keep-alive' \

-H 'Pragma: no-cache' \

-H 'Cache-Control: no-cache' \

-H 'sec-ch-ua: "Google Chrome";v="93", " Not;A Brand";v="99", "Chromium";v="93"' \

-H 'content-type: application/json' \

-H 'sec-ch-ua-mobile: ?0' \

-H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.63 Safari/537.36' \

-H 'tenant: as100' \

-H 'sec-ch-ua-platform: "Linux"' \

-H 'Accept: */*' \

-H 'Origin: https://as100.cymmetri.in' \

-H 'Sec-Fetch-Site: same-origin' \

-H 'Sec-Fetch-Mode: cors' \

-H 'Sec-Fetch-Dest: empty' \

-H 'Referer: https://as100.cymmetri.in/' \

-H 'Accept-Language: en-GB,en-US;q=0.9,en;q=0.8' \

-H 'Cookie: deviceId=fa83c4b1-7c85-467d-9b46-ffbc70efad97; Correlation=9928D5133AED419CBC01591B56483953; app_73e5c5f8-276b-47bb-a6a5-b6f82a779d79=e689a8da-faa7-46f5-9c7a-2800abdd206a; device=cf7bbf2a-161c-11ec-b3ec-39287c680726' \

--data-raw '{"password":"U2FsdGVkX191zbRQpSQz+rdxyAacEqD1G5Mx5wKtPV5ElwKZu7/TFHFLuCNH+v63G8k7sTFDa5gNYG9SQ+0ix4eZdTvLcJbELGm2yjUWjx2a6jH3JnP/USl2efCC9nDvufmqUhSbIPA0Nc1PZUqM+PPk+TpCFSoKtKwBPWeBa/LYjlYt11u++aTuVGsd/rOaWJxqINPRHIk6Ax89LfhM8+H6VKc4+ybfearoCJgHWCPE/X566hiYZJEKcMGe7u0OpUzGUMlyguBtfYlWlT7tcdP6x/rXlqs8vNTLk/HboYLv10UkB0ifsQ64c7fSQ/ofZKjQlqehpP4+SzIi4OiqRQikP9MOkKZWl9YJdGXZs+mUuzfEs9UGINMYBk1hSCq6xGb9mfE0vyFeVAyY/6oGgQ==","login":"totp","userId":"6214def0a251e06721ed8594"}' \

--compressed

Sample Response:

On success:

{"success":true,"data":null,"timestamp":"11-Mar-2022 01:40:38","message":null,"errorCode":null}

On failure:

Response 1#

{"success":false,"data":null,"timestamp":"11-Mar-2022 01:39:40","message":null,"errorCode":"AUTHSRVC.PASSWORD_COMPOSITION_RULE_VIOLATION"}

RESTful API – New Application count API (7 days)

Purpose: This API is used to get count of application

URL: http://<tenant_url>/api/selfservice/newApplicationsCount

Method: GET

Example Request:

curl --location --request GET 'http://localhost:8080/api/selfservice/newApplicationsCount' \

--header 'Connection: keep-alive' \

--header 'Pragma: no-cache' \

--header 'Cache-Control: no-cache' \

--header 'sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="99", "Google Chrome";v="99"' \

--header 'Accept: application/json' \

--header 'content-type: application/json' \

--header 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJhZG1pbiIsImRlbGVnYXRlZSI6bnVsbCwiZGVsZWdhdGVlSWQiOm51bGwsImZpcnN0TG9naW4iOmZhbHNlLCJyb2xlcyI6WyJPUkdfQURNSU4iLCJVU0VSIl0sInRlbmFudElkIjoiZ2s0MCIsImV4cCI6MTY0Njc0OTkzMiwidXNlcklkIjoiNjE3MDE1YTNjMDQ4MTc1NmI3OThhY2EyIiwiaWF0IjoxNjQ2NzQzOTMyfQ.puFKgrNoHZtRl6P4LxzFd9KQM_-EB-45DqqP4zywws8' \

--header 'sec-ch-ua-mobile: ?0' \

--header 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.51 Safari/537.36' \

--header 'sec-ch-ua-platform: "Linux"' \

--header 'Sec-Fetch-Site: same-origin' \

--header 'Sec-Fetch-Mode: cors' \

--header 'Sec-Fetch-Dest: empty' \

--header 'Referer: https://gk40.cymmetri.in/' \

--header 'Accept-Language: en-GB,en-US;q=0.9,en;q=0.8' \

--header 'Cookie: deviceId=6e4caedd-beaf-444c-9312-21b219bb3709; Correlation=B194B86832FB4683ABC43EA6077944E2; app_73e5c5f8-276b-47bb-a6a5-b6f82a779d79=e689a8da-faa7-46f5-9c7a-2800abdd206a; device=41b5bf50-9def-11ec-8665-953ee8af105c; Correlation=1B9449F921B043B9B513E99D253894CE; RefreshToken=b8ada8a1-d089-4a39-b3e1-72c04ce202fe; sessionId=130e95df-69a5-4462-a8b5-c04b53e97e64' \

--header 'Tenant: gk40' \

--header 'userId: 617015a3c0481756b798aca2'

Sample Response:

On success:

{"success": true,"data": 1,"timestamp": "11-Mar-2022 02:13:39","message": null,"errorCode": null}

RESTful API – Campaigns/access review search by campaign name

Purpose: This API is used to get list of campaign

URL: https://<tenant_url>/igsrvc/api/ig/campaign/execution/history/list-summary/reviewer

Method: POST

Example Request:

curl --location --request POST 'https://gk40.cymmetri.in/igsrvc/api/ig/campaign/execution/history/list-summary/reviewer' \

--header 'Connection: keep-alive' \

--header 'Pragma: no-cache' \

--header 'Cache-Control: no-cache' \

--header 'sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="99", "Google Chrome";v="99"' \

--header 'Accept: application/json' \

--header 'content-type: application/json' \

--header 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJhZG1pbiIsImRlbGVnYXRlZSI6bnVsbCwiZGVsZWdhdGVlSWQiOm51bGwsImZpcnN0TG9naW4iOmZhbHNlLCJyb2xlcyI6WyJPUkdfQURNSU4iLCJVU0VSIl0sInRlbmFudElkIjoiZ2s0MCIsImV4cCI6MTY0NzAxNDY2NywidXNlcklkIjoiNjE3MDE1YTNjMDQ4MTc1NmI3OThhY2EyIiwiaWF0IjoxNjQ3MDA4NjY3fQ.jP2BgjiOVUcdxhImVvdwy18puEylWSSOVHnWA_2hhJU' \

--header 'sec-ch-ua-mobile: ?0' \

--header 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.51 Safari/537.36' \

--header 'sec-ch-ua-platform: "Linux"' \

--header 'Origin: https://gk40.cymmetri.in' \

--header 'Sec-Fetch-Site: same-origin' \

--header 'Sec-Fetch-Mode: cors' \

--header 'Sec-Fetch-Dest: empty' \

--header 'Referer: https://gk40.cymmetri.in/' \

--header 'Accept-Language: en-GB,en-US;q=0.9,en;q=0.8' \

--header 'Cookie: deviceId=6e4caedd-beaf-444c-9312-21b219bb3709; Correlation=B194B86832FB4683ABC43EA6077944E2; Correlation=C27A4466A21046309B58FD53AEF4A2C5; RefreshToken=4ec80313-bed3-44e5-9081-33eb9ba301f2; sessionId=32ceee83-781e-45d6-9c2c-2acc8741a944' \

--data-raw '{

"filter": {

"campaignName": "Campaign For"

},

"keyword": "",

"pageNumber": 0,

"pageSize": 10,

"sortDirection": "ASC",

"sortOn": [

"startDate"

]

}'

Sample Response:

On success:

{

"data": {

"content": [

{

"executionId": "61a865c69c60c83eb2d2cf0e",

"name": "Campaign For Bug_w8z89q",

"description": "",

"campaignId": "61a8657c9c60c83eb2d2cf0c",

"revision": 1,

"iteration": 1,

"status": "COMPLETED",

"remarks": "",

"startMode": "MANUAL",

"startDate": "2021-12-02",

"endMode": "MANUAL",

"endDate": "2021-12-02",

"plannedEnd": "2021-12-05",

"totalAssignments": 41,

"pendingAssignments": 41,

"approvedAssignments": 0,

"rejectedAssignments": 0

},

{

"executionId": "6225c00ab21ac3024d5a1d91",

"name": "Campaign For Bug_w8z89q",

"description": "",

"campaignId": "61a8657c9c60c83eb2d2cf0c",

"revision": 1,

"iteration": 2,

"status": "COMPLETED",

"remarks": "",

"startMode": "MANUAL",

"startDate": "2022-03-07",

"endMode": "AUTO",

"endDate": "2022-03-10",

"plannedEnd": "2022-03-10",

"totalAssignments": 40,

"pendingAssignments": 40,

"approvedAssignments": 0,

"rejectedAssignments": 0

}

],

"pageable": {

"sort": [

{

"direction": "ASC",

"property": "startDate",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": true,

"descending": false

}

],

"pageNumber": 0,

"pageSize": 10,

"offset": 0,

"paged": true,

"unpaged": false

},

"totalPages": 1,

"totalElements": 2,

"last": true,

"first": true,

"sort": [

{

"direction": "ASC",

"property": "startDate",

"ignoreCase": false,

"nullHandling": "NATIVE",

"ascending": true,

"descending": false

}

],

"numberOfElements": 2,

"size": 10,

"number": 0,

"empty": false

},

"errorCode": null,

"message": null,

"success": true,

"timestamp": "11-Mar-2022 02:38:11"

}

API Response Codes

API

Status

Error Code

Message

Create API

200

OK

500

Internal Server Error

401

Unauthorized

403

Forbidden

404

Not Found

Update API

200

OK

500

Internal Server Error

401

Unauthorized

403

Forbidden

404

Not Found

Time Based Config
Email Config
Suspend Config
Reset password OTP Config
User Decommission Config
Syslog Configuration
Webhooks Configuration
Application Request Config
Threshold Delete Config
Artefact - Audit log indicating a value updated in the log with time timestamp

Assigning Users to Groups

Assigning Users to a Group

Users once created in the Cymmetri platform can be assigned to a group. Assigning users to a group helps ease the administrative efforts to apply the same policies and assign applications to multiple users.

When assigning users to groups there are various approaches that can be used:

  • Adding User to Group (from the Group Page)

  • Assigning a Group to a User (from the User's Page)

  • Bulk Assigning Users to a Group (Using Group Assignment on Group Page)

Adding User to Group

First, the administrator needs to click on the group name and enter the configuration for the group.

Now Go to the Users Page and click on the +Add button to get a list of users to add to the group

3. Now click on the assign button next to the user you wish to add to the group. Once assigned the user can be seen on the Users page of the Group as shown below:

Assigning a Group to a User

For this approach, the Administrator needs to go to Identity Hub > User page and then select the user from the list to whom the group needs to be assigned

Go to the user's page, select the Groups menu and click on "+Assign New" button

This opens a pop up window where a list of all groups is visible

Click on the assign button and the group is assigned to the user or you may say the user becomes a part of the group

Bulk Assigning Users to a Group

For this approach, the Administrator needs to go to Identity Hub > Group page and then click on the Group Assignment button

A screen pops up that lets you select the CSV file you want to upload to import the users that need to be assigned to the group. This CSV file needs to have one column that contains the login id of users; Upload the CSV file, you may also use the sample data file available and modify it to match your user's login id.

Once the file is selected and uploaded, next you need to select the group to which you want to assign the users.

After selecting the group the column in the csv file needs to be mapped with the Cymmetri login column.

Once mapped click on the import button and the users would be mapped to the assigned group provided the login id is correct

Results of successfully Imported Users, Duplicate Users, or any error that occurred during import can be seen in the Logs > Import History page

Password Policy

What is a Password Policy?

A password policy is a set of rules and requirements established by an organization or system to govern how users create and manage their passwords.

The purpose of a password policy is to enhance security by promoting the use of strong, unique passwords and minimizing the risk of unauthorized access.

In Cymmetri, only the admin can create a password policy bby navigating to the authentication section and then in password policy.

Upon landing the user can view a default Cymmetri password policy which cant be deleted or deactivated.

To create a new password policy, the admin clicks on the add new button on the top right corner of the page.

The user has to fill in the password policy form with the below details

  1. Policy Name - Name of the policy

  2. Description

  3. Conditional attribute type - Default - User (Non modifiable)

  4. Conditional attribute Name - Default - User Type (Non modifiable)

  5. Conditional attribute value - ( Consultant, Employee, Vendor)

After saving the detail, a new password policy is created. The next step is to define the password policy. This is done by clicking on the edit button in front of the record.

The admin can define the composition of the password. By rejecting

  1. Password equals Password

  2. Password which equals to LoginID

  3. Password which equals to first or Last Name

  4. Blacklisted Password

The admin can also establish the following parameters

  1. Numeric characters minimum count

  2. Password Length

  3. Special characters count

  4. Password History versions

  5. Alpha characters

  6. Uppercase characters

  7. Lowercase characters

  8. Characters not allowed in the password

In the "change" subsection the admin can also define:

  1. Password expiration days

  2. Password expiration warning from (no of days)

  3. Whether to change password on reset

Blacklisted Password

The administrator also has the capability to set prohibited passwords, preventing users from using those specific passwords.

Adaptive

Adaptive authentication is an advanced security measure that assesses various factors and context elements in real-time to determine the level of risk associated with a user's access attempt.

Based on this risk assessment, the authentication system can dynamically adapt its level of scrutiny and request additional verification steps if needed. This approach enhances security while minimizing disruption for legitimate users.

In Cymmetri there are various adaptive checks that the admin can enable for additional factor of authentication.

  1. Device Trust Check - If enabled, Cymmetri will check if the device being used to perform action on the Cymmetri portal, has been trusted by the user

  2. User Behavior - Cymmetri determines whether the behavior of user matches with the known behavior pattern of the user over time

  3. Blacklisted IP - Maintains a blacklist of IP addresses that are known to be sources of unauthorized access, hacking attempts, or other malicious activities

  4. Blacklisted Location - Cymmetri maintains a list of locations from which the administrator wishes to restrict access of the portal

  5. Short Lived Domain - Cymmetri checks the email address domain of the user with a database of known providers of short-term or disposable email addresses

  6. Impossible travel scenario - Tracks the change in location of user attempting an action over a short period of time and flagging if, system deems the pattern to be impossible.

The admin can enable these checks as per the business use case

To navigate to the adaptive settings page, click on the "Go to settings" button on the top right corner of the page.

IP Address Checks

Administrators can include an IP address in the blacklist by following these steps:

Enable the "IP address Check" radio button at the top of the page, input the IP address into the "Blacklisted IP address" field, and press enter. The specified IP will be added to the list. To synchronize the list with the database, click the "Sync Now" button.

You can select additional actions when module detects an anomaly. They are the following:

  • Ask additional MFA and notify - If an MFA rule has been established and adaptive authentication is activated for it in the MFA section, when a user attempts to log in with a blacklisted IP address, the user will be prompted for additional factor(s) for authentication as defined by the rule. Additionally, the user will receive email notifications regarding the login activity.

  • Only Notify - This option solely sends a notification to the user about the login activity.

  • Block user and notify - This option not only blocks the user upon a login attempt with a blacklisted IP but also notifies the user on their registered email ID.

Device Trust

Define how Cymmetri determines if a device is trusted for the user and allows to define behavior of authentication in Cymmetri, in case of untrusted device

The admin can define

  1. No of successful authentication attempts

  2. Number of devices per user

  3. Number of days

  4. Additional action when module detects anomaly

  • Location based checks

Organizations can maintain a list of blacklisted locations as part of their adaptive authentication strategy to enhance security measures and mitigate potential risks

The admin can select the blacklisted location on this page. Also additional actions on these checks can be selected.

  • Impossible Travel Scenario

Track the changes of location from which the user attempts to perform actions on the portal over a short period of time and flags an action attempt

The admin can configure the:

  1. Check Windows(in hrs)

  2. Average Distance (in Km)

  • Short lived Domain Checks

Checks the .email address domain of the user with a database of known providers of short-time or disposable email addresses

The admin can Sync the database where the domains are stored and updated

  • User behavior checks

Cymmetri determines whether the behavior of user matches with the known behavior pattern of the user over time

The admin can select the required checks to verify the consumer behavior:

  1. Unusual time of Login

  2. Unusual number of Login failures

  3. Unusual keystrokes pattern

The admin can enable, configure and save these adaptive checks individually as and when required.

Configuring Connector Server

Connectors can be deployed in two ways:

  • Local connectors are deployed to a Cymmetri instance. This is the usual way how connectors are used. The connector is executed inside a Cymmetri instance, has the same lifecycle (start/stop), etc. Cymmetri can detect local connectors automatically and overall the connector management is easier.

  • Remote connectors are executed in a different process or on a different node than Cymmetri instance. Remote connectors are deployed to a connector server. There may be need to use a remote connector e.g. to access a file on a remote system (e.g. in case of CSV connector) or because of platform incompatibilities (e.g. .NET connectors)

Connector is not developed as local or remote. The placement of the connector is a deployment-time decision. There is just one connector package that can be deployed locally or remotely.

A connector server is required when a connector bundle is not directly executed within your application. By using one or more connector servers, the connector architecture thus permits your application to communicate with externally deployed bundles.

Connector servers are available for both Java and .NET.

A Java connector server is useful when you do not wish to execute a Java connector bundle in the same VM as your application. It may be beneficial to run a Java connector on a different host for performance improvements if the bundle works faster when deployed on the same host as the native managed resource. Additionally, one may wish to use a Java connector server under a Java remote connector server in order to eliminate the possibility of an application VM crash due to a fault in a JNI-based connector.

The use of .NET connector server is especially useful when an application is written in Java, but a connector bundle is written using C#. Since a Java application (e.g. J2EE application) cannot load C# classes, it is necessary to instead deploy the C# bundles under a .NET connector server. The Java application can communicate with the C# connector server over the network, and the C# connector server serves as a proxy to provide to any authenticated application access to the C# bundles deployed within the C# connector server.

Java Connector Server

Installing a Java Connector Server

Minimum Requirements:

  • Java 1.6 or later for 1.4.X.Y / Java 1.8 for 1.5.X.Y

  • Refer to your Java connectors to determine if there are any additional requirements

Create your execution environment

  • Download the Connector Server package

  • Unzip it in a directory of your choice (e.g. /usr/jconnserv) on the host where you wish to run the Java connector server

Test your execution environment

From the directory created above, run the Java connector server with no arguments to see the list of command-line options:

  • Linux / MacOS: ./bin/ConnectorServer.sh

  • Windows: \bin\ConnectorServer.bat

You should see the following output:

Usage: 
  Main -run -properties 
  Main -setkey -key  -properties 
  Main -setDefaults -properties 

Configure your Java connector server

  • Run the connector server with the setkey option as described below to set your desired key into your properties file

    • Linux/ MacOS: ./bin/ConnectorServer.sh -setkey <key> -properties conf/ConnectorServer.properties

    • Windows: bin\ConnectorServer.bat /setkey <key> /properties conf\ConnectorServer.properties

  • For all other properties (e.g. port), edit the conf/connectorserver.properties manually. The available properties are described in the connectorserver.properties file.

Running your Java connector server

Run the server by launching with the -run option:

  • Linux / MacOS: ./bin/ConnectorServer.sh -run -properties conf/ConnectorServer.properties

  • Windows: bin\ConnectorServer.bat /run -properties conf\ConnectorServer.properties

Installing Connectors on a Java Connector Server

To deploy a Java connector:

  • Copy the Java connector bundle jar file into the bundles directory in your Java connector server directory

  • If necessary, add to the classpath any 3rd party jars required by any Java connector

  • Restart the Java connector server

Using SSL to communicate with connector servers

The following steps are necessary to successfully communicate with a connector server using SSL:

  • Deploy an SSL certificate to the connector server's system.

  • Configure your connector server to provide SSL sockets.

  • Configure your application to communicate with the communicate with the connector server via SSL.

Configure your application to use SSL

Refer to your application manual for specific notes on how to configure connections to connector servers. You will need to indicate to your application that an SSL connection is required when establishing a connection for each SSL-enabled connector server.

Additionally, if any of the SSL certificates used by your connector servers is issued by a non-standard certificate authority, your application must be configured to respect the additional authorities. Refer to your application manual for notes regarding certificate authorities.

Java applications may solve the non-standard certificate authority issue by expecting that the following Java system properties are passed when launching the application:

  • javax.net.ssl.trustStorePassword For example, -Djavax.net.ssl.trustStorePassword=changeit

  • javax.net.ssl.trustStore For example, -Djavax.net.ssl.trustStore=/usr/myApp_cacerts

Or, instead, the non-standard certificate authorities may be imported to the standard ${JAVA_HOME}/lib/security/cacerts.

.NET Connector Server

Installing a .NET Connector Server

Minimum Requirements:

  • Windows Server 2003 or 2008

  • .NET Framework 3.5 or higher

  • Refer to your .NET connector to determine if there are any additional requirements

Execute ServiceInstall.msi. Just follow the wizard. It will walk you through the whole process step by step. Upon completion, the Connector Server will be installed as a windows service.

Configuring the .NET Connector Server

Start the Microsoft Services Console. Check to see if the Connector Server is currently running. If so, stop it. From a command prompt, set the key for the connector Server. This is done by changing to the directory where the connector server was installed (by default: \Program Files\Identity Connectors\Connector Server) and executing the following command:

ConnectorServer /setkey <newkey>

where <newkey> is the value for the new key. This key is required by any client that connects to this Connector Server.

Look through the configuration file and inspect all settings. The most common things to change would be the port, trace, and ssl settings.

Additional Notes about configuration

The port, address, and SSL settings are in the tag called AppSettings, and look like this:

<add key="connectorserver.port" value="8759" />
<add key="connectorserver.usessl" value="false" />

<add key="connectorserver.certificatestorename" value="ConnectorServerSSLCertificate" />
<add key="connectorserver.ifaddress" value="0.0.0.0" />

The port can be set by changing the value of connectorserver.port. The listening socket can be bound to a particular address, or can be left as 0.0.0.0. To setup to use SSL, you must set the value of connectorserver.usessl to true, and then set the value ofconnectorserver.certifacatestorename to your the certificate store name.

You will need to record for use later the following information regarding your connector server installation:

  • Host name or IP address

  • Connector server port

  • Connector server key

  • Whether SSL is enabled

Changing Trace Settings

Trace settings are in the configuration file. The settings look like this:

<system.diagnostics>
  <trace autoflush="true" indentsize="4">
     <listeners>
       <remove name="Default" />
       <add name="myListener" type="System.Diagnostics.TextWriterTraceListener"
  initializeData="c:\connectorserver2.log" traceOutputOptions="DateTime">        
         <filter type="System.Diagnostics.EventTypeFilter" initializeData="Information" />
       </add>
    </listeners>
  </trace>
</system.diagnostics>

The Connector Server uses the the standard .NET trace mechanism. For more information about the tracing options, see Microsoft's .NET documentation for System.Diagnostics.

The default settings are a good starting point, but for less tracing, you can change the EventTypeFilter's initializeData to "Warning" or "Error". For very verbose logging you can set the value to "Verbose" or "All". The amount of logging performed has a direct effect on the performance of the Connector Servers, so be careful of the setting.

Any configuration changes will require the connector server to be stopped and restarted.

Running the .NET Connector Server

The best way to run the Connector Server is as a Windows service. When installing, the Connector Server is installed as a Windows service. This should be fine for most installations.

If for some reason, this is not adequate, the connector server may be installed or uninstalled as a Windows service by using the /install or /uninstall arguments on the command line. To run the Connector Server interactively, issue the command:

ConnectorServer /run

Installing Connectors on a .NET Connector Server

To install new connectors, change to the directory where the Connector Server was installed, and unzip the zip file containing the connector there. Restart the Connector Server.

Running Multiple Connector Servers on the Same Machine

To install additional Connector Servers on the same machine, download the Connector Server zip file from the downloads section. Create a directory to install to, and unzip the file there. Edit the configuration file as described above ensuring that you have a unique port. You may also want to make sure that the trace file is different as well. You can then run the additional Connector Server interactively or as a service.

Push Notification as MFA for Blacklisted IP check on Login
Email on user's registered Email ID

1.3.3.1
1.4.5.1
1.5.0.1
1.5.1.0