The Jade IDE doesn't currently do any usercode/password validation or enforcement. It does provide Development Security Library (DSL) hooks, which some teams have coded to validate the usercode/password credentials entered on the Jade IDE logon screen against an Active Directory (AD) or similar user credentials authentication mechanism. Any enhancements to the DSL hooks to support teams adding SSO support into their DSL library would need to be implemented in such a way that it doesn't break any of the existing usages of the current DSL mechanism.
Cheers, BeeJay.
Any thoughts expressed are my own and in no way reflect the views of my employer. If this reply includes any sample code, or other changes such as registry key settings, I believe that this information is accurate and reliable and has been prepared with care but give no guarantee that the sample code or suggested changes will be free of defects or errors. No responsibility or liability, financial or otherwise, is accepted for any consequences arising out of the use of any sample code, registry changes, etc, including loss of profits, indirect, special or consequential losses or damages.
The Jade IDE doesn't currently do any usercode/password validation or enforcement. It does provide Development Security Library (DSL) hooks, which some teams have coded to validate the usercode/password credentials entered on the Jade IDE logon screen against an Active Directory (AD) or similar user credentials authentication mechanism. Any enhancements to the DSL hooks to support teams adding SSO support into their DSL library would need to be implemented in such a way that it doesn't break any of the existing usages of the current DSL mechanism.
Cheers,
BeeJay.
Any thoughts expressed are my own and in no way reflect the views of my employer. If this reply includes any sample code, or other changes such as registry key settings, I believe that this information is accurate and reliable and has been prepared with care but give no guarantee that the sample code or suggested changes will be free of defects or errors. No responsibility or liability, financial or otherwise, is accepted for any consequences arising out of the use of any sample code, registry changes, etc, including loss of profits, indirect, special or consequential losses or damages.