Special Characters limitations in connection string
Hi Community, does anyone have a list of special characters that OneStream does not allow to be used in passwords for service accounts used for direct connections?
Thank you
Forum Discussion
I'm still not entirely sure where you're handling this connection string (in the Server Config Utility? In custom code?), but I believe it has to be an ADO.NET connection string, so any limitations of that format will apply. You should pay attention to ampersands and particularly semicolons, which will have to be escaped. I don't know if the Oracle driver has any additional requirements.
We are populating the connection string when creating a Local Gateway Connection to a Data Source, as part of the Smart Integration Connector setup.