Access Manager 5.1 Beta Now Available!

6 Likes

Dear Access Manager Enthusiast,

 

We are excited to announce the Beta release of Access Manager 5.1, and we invite you to be an exclusive participant in our Closed Beta program. This closed testing phase is reserved for registered participants, ensuring that you are among the first to experience the latest features and enhancements before the official release.

 

Key Features of Access Manager 5.1 Beta:

  1. Intuitive, Refreshing, and Responsive Administration Console: Immerse yourself in a redesigned administration console that is not only intuitive but also refreshing and highly responsive. We've focused on enhancing the user experience to make managing configurations smoother and more enjoyable.
  2. Built with Angular: Access Manager 5.1 Beta is built with Angular, bringing a modern and robust framework to the table. This update ensures a seamless and efficient user interface, setting the stage for a more dynamic and interactive experience.
  3. Automation with REST APIs: Unlock the full potential of automation with the introduction of REST APIs. Access Manager 5.1 Beta empowers you to automate various tasks, streamlining your workflows and providing greater flexibility in managing configuration.
  4. Auditing for Configuration Changes: Gain deeper insights into your system with the new auditing feature for configuration changes. Track and review every modification made to the system settings, enhancing transparency and security in your access management process.

 

Why Participate in the Beta Program:

  • Early Access to Cutting-Edge Features: As a Beta participant, you get a sneak peek into the latest enhancements and features before the official release. Be among the first to explore and leverage the advanced capabilities of Access Manager 5.1.
  • Direct Influence on the Final Release: Your feedback is invaluable to us. By participating in the Beta program, you have the opportunity to shape the final version of Access Manager 5.1. Your insights, suggestions, and bug reports will directly contribute to refining the product for a smoother user experience.

 

To participate in the Closed Beta, please ensure that you are a registered participant. If you haven't registered yet but are keen to be part of this exclusive testing phase, kindly drop an email to nam@opentext.com, expressing your interest.

 

What Next:

  • Access Details: Registered participants will receive an email from noreply@opentext.cloud with NAM 5.1 Beta shared folder. The shared folder will contain Beta binaries and other artefacts. In case of any issues with the access, please reach out to nam@opentext.com.
  • Beta Program Duration: The Closed Beta program is scheduled to conclude on February 9th, one month from today. Take advantage of this limited-time opportunity to explore the features and provide your feedback.
  • Support and Feedback: If you encounter any issues during your Beta testing, you can register a support case with OpenText support or reach out to nam@opentext.com for assistance. Your valuable feedback is crucial to us; share your thoughts by sending an email to nam@opentext.com.
  • Community Engagement: Engage with the Beta community by participating in discussions. You can post in this community thread or post in the  Access Manager 5.1 Beta Discussions dedicated page for more extensive discussions.

 

Thank you for being a part of the Access Manager community.

 

Best regards,

Access Manager Beta Management Team

Labels:

Announcement
New Release-Feature
Comment List
  • Join the discussions on Our Access Manager 5.1 Beta Discussions Community Page!

    We're excited to invite you to our Beta discussion community page!

     Access Manager 5.1 Beta Discussions 

    Let's use this vibrant space for sharing your thoughts, collaborating and engaging in meaningful discussions. Your insights and contributions are invaluable. Let's connect and discuss. See you there!

  • This is inefficient. Collaboration and issue tracking would be greatly facilitated by creating a new, private discussion forum as has been done in past NAM and other NetIQ product betas. Helps avoid/limit the amount of duplicate issues being raised. Also allows for testers to chime in on other people’s issues, which helps OpenText better gauge criticality and even allows other customers to potentially expose additional details in their own findings concerning that issue. Email to generic inbox doesn’t allow that. Posting “comments” to a single public forum article is silly and not scalable way of reporting issues. Dumping the responsibly to instead create cases on a PSE/DSE like ours isn’t fair or efficient, and also doesn’t allow for collaboration and awareness on issues raised by fellow beta testers.

  • Thanks for pointing this out, Stefan. I agree, discussions between the Beta participants cannot be done through emails. For the community engagement, let me start a user discussion thread where all of the participants can participate. Other community engagement possible is through access manager list group, where everyone can see each other's emails and queries. For the issues prioritization and addressal, we would still prefer the cases or email to nam@opentext.com, as tracing through the community discussion is not feasible and effective.

    Actually, the announcement had support and community engagement details mentioned. Just pasting again:  

    • Support and Feedback: If you encounter any issues during your Beta testing, you can register a support case with OpenText support or reach out to nam@opentext.com for assistance. Your valuable feedback is crucial to us; share your thoughts by sending an email to nam@opentext.com.
    • Community Engagement: Engage with the Beta community by participating in discussions. You can post in this dedicated community thread or join the Access-Manager-List group for more extensive discussions.
  • This closed beta urgently requires its own private forum for logging issues and collaborating with other participants. Sending emails to a generic inbox for each discovered issue is not efficient or conducive to properly tracking items.

Related
Recommended