02-14-2023 12:06 PM
Hello,
Just wondering if SQL Express would be a platform supported by Hyland to run the Operational Database for the Hyland IdP?
I also noticed that there have been additional tables added to the Operational Database in new versions of the Hyland IdP. Originally my understanding was that it is a "runtime database" and that no data is stored in the tables permanently. Is this still accurate or does it now retain data in the new tables?
Thanks!
02-24-2023 06:09 AM
Hey
The team was able to test and verify locally that SQL Express works for the Hyland IdP Operational database.
A couple other things to note, as this testing was focused on quickly getting a working environment. Please follow security rules as per the policies for your environment. This also was not tested under a heavy load like we would for the full version of SQL or Oracle. So while we don't forsee any issues, use at your own risk.
A few things they did during setup that might be slightly different:
Outside of that, it was just creating the Hyland IdP database through the Admin UI or CLI as you would normally with SQL.
May I ask why you would use SQL Express? For instance an added layer of security or separation from the OnBase database?
If you have any trouble or questions, please let me know.
02-16-2023 08:34 AM
Hi
I am reaching out to our Identity and Access Management team to see if SQL Express is supported for the Hyland IDP's Operational Database. We will get back to you as soon as we have information or subsequent questions.
Thanks,
~Alan
02-22-2023 07:07 AM
Any update on this? We are waiting on an answer to determine the architecture for a deployment.
Thanks!
02-22-2023 08:31 AM
Hi
Here is some information from Product Management:
SQL Express testing should be completed in the next few days. It does seem to be working but there may be some specific permissions or settings that would need to be changed. However, the team was able to setup it up and as long as the connection string is working, then Hyland IdP is working. Any caveats will be documented for all customers to see.
As of Hyland IdP v3.1.0 - The Hyland IdP now uses a persistent ID from a third-party provider instead of the username as the unique identifier to locate and provision users (IAMPRO-14). This requires us to store mapped user and thus persistent data. They can be mapped on login or manually imported. Either way, it requires persistent data for the associated ID. More information can be provided if you need it.
We will keep you informed when testing is complete.
Thanks for your patience,
~Alan
02-23-2023 11:34 AM
Thank you for the update! I look forward to seeing the documentation when it is ready. Thanks!
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.