Article Details
| Id: | 10926 |
| Product: | finPOWER Connect |
| Type: | NEW |
| Version: | 1.06.07 |
| Opened: | 14/02/2013 |
| Closed: | 18/02/2013 |
| Released: | 27/03/2013 |
| Job: | J011119 |
 High Importance |
|
 Breaking Change |
|
Users; Integrated Security changes made to allow User password to be defined even when using Integrated Security
If a database is set up in MS SQL Server and Users are configured to use Integrated Security and this database is then copied to an MS Access database (e.g., in a test environment), no Users can login since Integrated Security is only supported for MS SQL Server databases.
The Users form will not show the 'Integrated Security' section on the Login page thereby not allowing this flag to be removed from existing Users.
To resolve this issue, the following changes have been made:
- The 'Integrated Security' section is not always shown on the Login page of the Users form if one or more Users is configured to use Integrated Security.
- Administrators can no longer use Integreated Security.
- Saving of Users will fail. Existing records will fail login.
- A password can now be set for a User from the Users form, even when using Integrated Security.
- When a User attempts to login to a database that does not support Integrated Security (or accessing via the Web), this password will be used instead. If no password is defined then the login will fail.
- Error messages as a result of attempting to log in using Integrated Security to a database that does not support Integrated Security will include the text 'Failed to load current User (Integrated Security disabled since this is not an MS SQL Server database)'.
- Saving a User in a non MS SQL Server database where no password has been set is no longer allowed, regardless of whether the User is configured to use Integrated Security.
- An action to clear all Users' 'Use Integrated Security' setting has been added to the Users form.