One password across all applications
Synchronize passwords from Windows / AD / Azure AD to your ORACLE applications
Create seamless synchronization to enable more security for your users
When a Windows/AD password is changed FastPass synchronizes the password to all the user’s Oracle systems
- The password is updated within 10 seconds at the target system
- The user can have different user-ids for Windows and Oracle
- The user can have multiple Oracle accounts to be synchronized
- FastPass can handle many Oracle instances simultaneously (more than 100)
- Fast and easy implementation with our assistance
- The Windows password is intercepted at the domain controllers to be forwarded to FastPass in encrypted format
Some organizations have specialty needs when it comes it to giving users a solution where they can specifically reset or unlock an Oracle password.
Some also want users to only have one password across multiple systems like Oracle and Active Directory.
With FastPass you can achieve this efficiency with password synchronization.
Easy to use self-service portal for all systems
Direct Oracle password reset
Reduce workload in your Help Desk and strengthen security
HOW IT WORKS
FastPass Sync provides easy integration into multiple Oracle systems from a single implementation.
The stored procedure has to be installed before the connector will work.
We require the following parameters to be configured in the Administration Client to be able to access an oracle server.
Oracle Password Reset Tool Pricing
FastPass SSPR and Synchronization is an enterprise product for cloud and on-premises competitively priced, based on the number of user-ids and functionality
- Easy to use self-service portal for all instances
- Supports all Oracle variations, and an unlimited number of Oracle instances
- Functionality as FastPass Enterprise
- Synchronize AD passwords to Oracle passwords
FastPass V4 - Secure Enterprise Passwords
FastPass V4 brings comprehensive password protection to secure organizations. Making passwords complex, avoiding the use of dictionary passwords and popular phrases as part of the password, changing the password regularly, and protecting the password processes will make your organization unattractive to hackers.
Frequently Asked Questions
The fundamental requirement for FastPass Sync for Oracle is a single Virtual Windows server (versions 2019-2022). Additionally, FastPass Interceptor needs to be installed on all Domain Controllers to facilitate Windows password interception. Finally the Oracle Instant Client https://www.oracle.com/database/technologies/instant-client/downloads.html needs to be installed on the server.
No special software installation is required on the Oracle side. The integration consists of functions and procedures. They all need to be added to the database at hand. These are noted in detail on the Oracle Integration Notes document available on the support site. On the FastPass side the Oracle Instant Client for Windows is needed.
Yes, FastPass supports encrypted connections to Oracle. To enable this feature, ensure that the setting SQLNET.ENCRYPTION_CLIENT=required is configured on the client side. This setting mandates the use of an encrypted connection, thereby enhancing the security of the data transmission to and from the Oracle database.
Yes, FastPass is compatible with Oracle RAC databases. To ensure proper functionality in this environment, the only requirement is a slight modification to the connection string. Once adjusted, FastPass should operate effectively within the Oracle RAC framework.
For effective integration with IBM iSeries, FastPass requires the OS/400 version V4R5 or above. Additionally, a dedicated service account needs to be set up to enable FastPass's connection to the system. It's also important to ensure that the Password Level on the iSeries system is set to at least level 2 to facilitate proper synchronization with FastPass.
FastPass primarily uses the available API through SQL for facilitating password resets in Oracle systems. This method allows for effective and secure password management within the Oracle database environment.
FastPass is designed to work with Oracle versions that are newer than 2003, starting from version 10G onwards. This compatibility is due to FastPass's utilization of very general functions available in these newer Oracle versions.
Yes, FastPass is equipped to handle password management in Oracle E-Business Suite. The software package includes a special set of Oracle procedures specifically designed for EBS, ensuring that it works out of the box without the need for additional customizations.
FastPass's ability to handle users in custom applications varies. For applications using native Oracle users, FastPass supports them out of the box. However, if your application uses custom usernames and passwords stored in specific fields and tables, compatibility depends on how the application encrypts or hashes passwords. If the passwords can be set using SQL, FastPass can be customized to manage them. If it is necessary to call other function outside SQL, then the SSH or API connector might be the better way. We recommend contacting FastPass for a Proof of Concept (POC) to discuss your application's specific requirements in detail.
In most cases, password synchronization with Oracle systems through FastPass is completed in under 15 seconds. This duration can vary depending on factors like hardware specifications, the number of users, and the number of target systems. During peak times, such as Monday mornings following a holiday break, synchronization may take slightly longer, typically ranging from 30 seconds to 1 minute, due to higher system loads.
Completely aligning the password policies between Active Directory and Oracle is not always feasible due to certain inherent differences. However, with FastPass Password Filter, these discrepancies can be effectively managed, ensuring smoother operation. For FastPass Sync customers, this filter is provided free of charge.
Yes, FastPass has a user mapping engine for that exact purpose. Usually this is the case, either for some or all users. Sometimes we can make the mapping manually using Active Directory data, a different field, email address, UPN name or parts of the SAMAccountname.
In other cases we get data from an Identity System and in yet other cases we get data from the target system and map on e.g. Email address.
Contact us to find the right solution.
The FastPass Sync engine is built for load, spawning out multiple threads to handle load. We have customers with over 95 target systems.
By default, FastPass will unlock the account.
FastPass is equipped with a resilient retry system for such scenarios. By default, it will attempt to retry the synchronization process 10 times, with a 2-minute interval between each attempt. These retry settings are adjustable to better suit your specific environment. Moreover, in instances where the Oracle system experiences an extended downtime, FastPass provides an option to manually trigger a synchronization for a chosen time interval. However, this feature needs to be enabled, as it involves data deletion considerations.
FastPass is designed for robustness and stability, ensuring that a downtime in one system does not halt or significantly slow down the overall synchronization process. Instead, only the synchronization with the affected system will be subject to retries as outlined previously. This ensures that the synchronization with other systems continues unaffected.
Absolutely, FastPass is fully compliant with FIPS (Federal Information Security Management) 140-2 standards, starting from version 4.0 onwards. We utilize a 256-bit AES algorithm for encryption and a PBKDF algorithm for hashing. This compliance extends across all FastPass components, from the Windows Client to the Server and Domain Controller parts, ensuring robust security throughout the system.
Indeed, FastPass's cloud operations are proudly certified with Cyber Essentials Plus, affirming our commitment to robust cybersecurity practices.
Yes, FastPass provides the functionality to automatically delete user data and restrict access as needed. This is achieved by FastPass regularly checking the source user repository. User data can be set to be automatically deleted under certain conditions, such as if the user account is deleted or disabled, is no longer a member of a group authorized to use FastPass, or becomes a member of a group specifically designated for deletion. This ensures that user data management aligns with the current status and permissions within the organization. Please note that the users history actions are kept in the Audit log.
Absolutely, FastPass includes a customizable list of prohibited passwords to help enhance security. We provide a top list of commonly used weak passwords that we recommend you utilize as a starting point. Additionally, it's a good practice to expand this list by adding specific terms related to your company, such as the company name, product names, and other relevant terms. This approach helps ensure users avoid common and potentially vulnerable passwords, thereby strengthening overall password security.
Yes, FastPass features a comprehensive and detailed audit log that meticulously records every action. This includes not only user activities but also all operations conducted within the Help Desk tool and the Admin interface. This extensive logging capability ensures thorough tracking and accountability for all interactions within the FastPass system, providing an essential tool for security and administrative oversight.
All personnel supporting FastPass cloud are as a minimum are BPSS checked and are annually trained on Data Protection and personal data best practice. They are also required to sign NDAs and the Information Security Policy and Data Protection policy. These policies are aligned with ISO 27001 / EU GDPR. Read more about GDPR and the Service Desk.
Absolutely. FastPass prioritizes data security, especially during data transit. One of our fundamental security measures is the mandatory use of SSL (Secure Sockets Layer) certificates for all communications. This ensures that any data exchanged between users and FastPass is encrypted, significantly enhancing security and protecting against data interception or unauthorized access during transmission. For Cloud operation TLS 1.2 is used.
Yes, FastPass ensures that all sensitive data is encrypted when stored in our database. This includes any data at rest within the FastPass system, providing an added layer of security against unauthorized access. For specific details on the types of data that are read, stored, and require write access within Active Directory and Entra ID, we recommend consulting the respective documentation. This information will give you a comprehensive understanding of our data handling practices and the security measures in place to protect your data at all times.
Yes, FastPass is fully compatible with LSA Protection. The FastPass Interceptor and Password Filter components are signed by Microsoft, ensuring compliance and functionality with LSA Protection enabled. Adhering to the Microsoft Security Development Lifecycle (SDL), FastPass integrates seamlessly with the Local Security Authority Server Service (LSASS), allowing for safe and secure password synchronization in environments where LSA Protection is applied.
FastPass does not support direct password synchronization from Entra ID (Azure AD) to other systems. This is because password synchronization requires identical hashing methods, a process currently specific to Microsoft's synchronization between Entra ID and Active Directory. However, FastPass offers alternative password management solutions, such as the Selective Password feature, where users can set passwords for one or more systems via the FastPass web portal.
FastPass ensures regular updates for optimal performance and security. For the server components, such as the SSPR backend and IVM, we typically release a major version upgrade once a year. Additionally, we provide 2-3 smaller updates annually, focusing on introducing new features and addressing bug fixes. It's important to note that the Windows Client, along with the Password Interceptor and Filter components, are designed to be backward compatible with the latest two major versions. This compatibility feature offers flexibility and ease during the upgrade process, ensuring a smooth transition for users and IT administrators.
FastPass adopts a version-based approach for our End-of-Life policy, focusing on Major and Minor releases. We offer support for the current Major release and the last officially released Major version. For instance, as of now, we support versions 3.6 and 4.0. This means that if you encounter any issues with version 3.6, our support team will assist you, including making necessary fixes to facilitate upgrades. However, we do not provide the same level of support for versions that are two Major releases behind the current one. To ensure continuous support, we recommend upgrading at least once every year, aligning with our Major version release cycle.
"The number of forgotten passwords per involved user per year has dropped from 1.6 to 0.3. This is an improvement of 83%!"
Receive an individual and specific overview of FastPass pricing
Get in touch with us today by filling up the form and our team will get back to you as soon as possible.