After upgrading to SBM 10.1.5.1 integrations that use the C++ API with SBM may require a password update or they stop functioning. SBM 10.1.5.1 made improvements around this authentication scenario and now a password is required for this integration user , and login attempts will be validated against the internal SBM database.
All functions provided by the JSON API honor SBM user privileges; additional privileges are not required to access the API functions. Requesting a Security Token
When SBM authentication is set to SSO + SBM forms + Internal or SBM Sessions + SBM forms + Internal and user session timeout is set, the JSON API will not authenticate the user . The sample out will look like the following: Status Code: 200
