Edge Documentation

This page answers Frequently Asked Questions (FAQ) about custom solutions for enPortal.

For FAQs about custom solutions in AppBoard, see the AppBoard Custom Solutions FAQ

Custom Solutions

Can enPortal Manage Password Rotation? Our customer uses Enterprise Password Vault module in Cyber-Ark's Privileged Identity Management (PIM) Suite for managing password rotation. If we want to integrate all password rotation into enPortal (such as Active Directory accounts for LDAP authentication, and passwords in Data Sources), is it possible for other tools/scripts to automate the process?

In order to consider the use of the third party application Cyber-Ark to manage your password rotation needs within enPortal, it best to explain where and how the passwords are stored within enPortal. enPortal makes use of a memory resident (or embedded) H2 database for some of its internal workings. One of these internal workings is password storage for the overall system and data source configurations. The only interface into the DB is through the enPortal GUI. This is due mainly to the persistent lock files of the database, and is part of the security measures used by enPortal. An interface could be constructed via JSP to allow a third party to interact with passwords within the database.

Can I integrate custom-built web applications and legacy applications that are not web-based?

AppBoard and enPortal integrate with custom-built web applications at the data layer and the web GUI layer. enPortal's Content Retrieval Service is designed to easily integrate web applications, and many integrations require minimal effort to build. The default rules support most applications that use basic authentication and do not use javascript to dynamically create content on the client. For such applications, integration can be achieved in minutes. If custom authentication support is required, such as typical form-based authentication, this can often be achieved in under a day or two by a web developer (knowledge of HTML and Javascript) who has taken the integration class. If the application requires additional rules to allow it to work within a portal view (such as preventing targeting the top frame), 1-2 days of work from a trained web developer may be required. In less common instances, it may take a trained web developer approximately a week of effort or advanced consulting services from Edge to integrate an application.

AppBoard and enPortal are also able to integrate with legacy applications that are not web-based via data adapters. Integration with non-web application GUIs is via an integration module (PIM) to Oracle/Sun Secure Global Desktop, a product that enables non-web applications to be accessed from any Java-enabled web browser.