• State Not Answered
  • Replies reply
    1
  • Subscribers subscribers
    14
  • Views views
    322
  • Users 0 members are here
  • Locked Locked
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problems with categories and Smartphone method

mguldner

AA 6.4.2

We have defined two additional categories so that we have "Default", "2-ZWEITGERÄT", "3-DRITTGERÄT". If a user enrolls to smartphones of the same OS (iOS or Android), only the second one works. If the user chooses the first one, no accept request is sent to the app and the user gets back to entering the username.

We found these combinations working/not working:

  • iOS1, iOS2 - iOS1 not working, iOS2 working
  • Android1, Android2 - Android1 not working, Android2 working
  • iOS, Android - both are working
  • Android, iOS1, iOS2 - Android not working, both iOS are working
  • iOS1, iOS2, Android - iOS1 not working, iOS2 and Android working
  • iOS1, Android, iOS2 - all three are working

It seems that as soon as 2 similar systems are defined in two consecutive categories, the device in the standard category does not work.

Is this a known problem? Is there an explanation for this behavior?

  • 0  

    Hello,

    My advice is to open a ticket with technical support for further investigation.

    Was this working well before?

    It could be due to this, but you are listing a couple of examples where this doesn't seem to apply:

    • You can enroll only one authenticator of one type for each category.

    So better to have this checked by TS.

    Thanks.

    Regards,

    Luciano Testa

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.