This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SQL Authenticating with Wrong Password

I'm in a test environment and I wanted to see what 1IM would do with a SQL import if the SQL user it's importing with has it's password changed. So I set up an import into some business role objects coming from a SQL Database. Ran the import as normal, everything worked correctly. Then I went into SQL and changed the SQL User account password to be something different so now 1IM has the wrong password. I expected the next time I tried to do a sync it would throw an error but what actually happened is that the sync continued as normal. I thought maybe something was cached so I restarted the SQL service and the 1IM service but the sync still completed successfully. Also, when I click on Target System in the Synchronisation Editor, it gives me an error saying it can't authenticate but when I run it, it does work. What is going on here? How is it importing from SQL while it has the wrong password?

Parents
  • One IM connects to the SQL Server automatically and downloads the new password. It's magic.
    No, I made that up. :)

    How are you authenticating? Windows integrated, or SQL auth? Based on your description, I think SQL auth. Behind the scenes, One IM constructs a connector string and encrypts it. For a sync, it decrypts the connection string and presents it.
Reply
  • One IM connects to the SQL Server automatically and downloads the new password. It's magic.
    No, I made that up. :)

    How are you authenticating? Windows integrated, or SQL auth? Based on your description, I think SQL auth. Behind the scenes, One IM constructs a connector string and encrypts it. For a sync, it decrypts the connection string and presents it.
Children
No Data