1 update [dbo].[FeatureToggles] set [FeatureLaunchId] = null
2 update [dbo].[FeatureToggles] set [IsLaunched] = 0
3 Delete from [dbo].[WebstoreFeatureToggles]
4 Delete [dbo].[FeatureLaunches]
Add feature launch
1 update [dbo].[FeatureToggles] set [FeatureLaunchId] = null
2 update [dbo].[FeatureToggles] set [IsLaunched] = 0
3 Delete from [dbo].[WebstoreFeatureToggles]
4 Delete [dbo].[FeatureLaunches]
Add feature launch
Go to azure
Search SCCSMTP001
click Open SaaS Account on publisher’s site
settings > sender authentication > click show more.
https://manage.fastly.com/home
Fastly
https://www.microsoft365.com/apps?auth=2&home=1
heart 1
Sign in to your account
change CloudConfigs FastlyEnableForNewInstallation value to false
update [dbo].[CloudConfigs] set[Value] = 'false' where [key] = 'FastlyEnableForNewInstallation'
restart app
convert string to type
simple Key, Value pair array
convert response object to Key value by Object entres
then go to Secret > select any value
eg: ApplicationSecrets-AzureWebJobStorage
secret value kept as encrypted
and authorized users can change the sensitive data from here. without hardcoding at the code level.
two types of jobs
1 Azure portal job (Keep)
2 operation Kubernetes (backup, upgrade, retry, extend trial)
eg:
now in App.config files don't keep any data,
all the details are kept in userSecretsFile.
userSecretsFile location is "C:\\home\\secrets.xml" (only use for Azure jobs)
by reading those data it will fill the appSettings Key value details
file inside secrets.xml
Problem : Single sign-on users unable to acess the Sana Platform APIs.
Solution: Intraduce the Personal Access Token feature
This feature is designed to help users who use Single Sign-On but can't access the Sana Platform APIs .
The problem arises because when you log in through Single Sign-On, user don't need to enter a password for the Platform portal.
This means these users can't use the "/api/v1/accounts/authentication-token" API to generate an "Access Token" and use other APIs.
Update Role permission>
after granting the permission ,usser able use the personal access token feature as folowing