You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was testing new features and new MS laps compatibility on v2. I noticed all settings are moved to SQL. I was once more setting up ISAM like in #94 but noticed the 'ClaimName' param is not defined anymore. Is it still possible to add it to the setting in database dbo.ConfigItems/Authentication?
The text was updated successfully, but these errors were encountered:
My apologies, we did have a plan to expose a setting for this but didn't make the cutoff for V2.
We will add this in a future release.
If you perform an in place upgrade from v1, with the ClaimName setting in place, it will be imported into the V2 database.
You can manually add it to the config key json that you identified. Just back up the existing value or the service may fail to start if it's incorrectly formatted.
Hi,
I was testing new features and new MS laps compatibility on v2. I noticed all settings are moved to SQL. I was once more setting up ISAM like in #94 but noticed the 'ClaimName' param is not defined anymore. Is it still possible to add it to the setting in database dbo.ConfigItems/Authentication?
The text was updated successfully, but these errors were encountered: