Resetting Admin App Configuration (Draft Update)

Environment: OnPrem

Admin App Version: >= 2.2.0

Note: Admin App version 2.2+, the encryption and decryption operation are using AES algorithm. So, it is very uncommon to encounter the "key and secret cannot be used in that state" issue.

Uncommon cases:

User missed to maintain/ retain the EncryptionKey while upgrading the application from version 2.2+ to latest version (Please refer the documentation on upgrading Admin App here)
Missing the encryption key on the appsettings.json after the first-time setup completed on Admin App 2.2+

Note: Please make sure to create new EncryptionKey using the following PowerShell command and update the appsettings.json with newly created value before running the first-time setup again on Admin App.

Generate Encryption Key

$aes = [System.Security.Cryptography.Aes]::Create()
$aes.KeySize = 256
$aes.GenerateKey()
$EncryptionKey = [System.Convert]::ToBase64String($aes.Key)

If user is in any of the above-mentioned situation, please follow the following steps to recover the application and force the first-time setup on Admin App.

Steps for Recovering the Application on Shared Instance mode

1) Clear Configuration Parameters & Force Admin App's First-Time Setup

Please make sure to stop ODS API and Admin App websites under IIS.
Connect to SQL Server on SSMS.
Select the EdFi_Admin database.

Execute following sql commands for clearing all the data records created during first time setup process.

Void first time setup updates

BEGIN TRAN   
DECLARE @ApplicationId INT;
 
SELECT @ApplicationId = ApplicationId FROM dbo.Applications WHERE ClaimSetName = 'Ed-Fi ODS Admin App'
 
DELETE FROM dbo.ClientAccessTokens WHERE EXISTS (
        SELECT 1 FROM dbo.ApiClients
        WHERE ClientAccessTokens.ApiClient_ApiClientId = ApiClients.ApiClientId
        AND Application_ApplicationId = @ApplicationId
)
    DELETE FROM dbo.ApiClients WHERE Application_ApplicationId = @ApplicationId
    DELETE FROM dbo.ApplicationEducationOrganizations WHERE Application_ApplicationId = @ApplicationId
    DELETE FROM dbo.ProfileApplications WHERE Application_ApplicationId = @ApplicationId
    DELETE FROM dbo.Applications WHERE ApplicationId = @ApplicationId    
    DELETE FROM adminapp.SecretConfigurations
	DELETE FROM [EdFi_Admin].[adminapp].[OdsInstanceRegistrations]
	UPDATE dbo.Applications set OdsInstance_OdsInstanceId = null  -- making sure to remove the foreign key constrain 
	UPDATE [EdFi_Admin].[adminapp].[ApplicationConfigurations] SET FirstTimeSetUpCompleted = 0 
	DELETE FROM dbo.OdsInstances
COMMIT  TRAN

Once successfully executed the above mentioned SQL script, please restart the Admin App website under IIS
Now browsing the Admin App will take user to the first time setup page
For recovering already created vendor applications on Admin App, user needs to manually update OdsInstance_OdsInstanceId column on dbo.Applications table to have default Ods instance id. On SharedInstance mode will be having only one OdsInstance on dbo.OdsInstances table.
Update Applications Expand source
```
DECLARE @odsinstanceid INT
SELECT TOP 1 @odsinstanceid = OdsInstanceId FROM [dbo].[OdsInstances]
Update [EdFi_Admin].[dbo].[Applications] set OdsInstance_OdsInstanceId = @odsinstanceid where OdsInstance_OdsInstanceId is null
```

Environment: Azure

Admin App Version: < 2.2.0

Issues

The application deployed and First-Time setup was successful, however you are unable to proceed further with the Admin App settings page or you get an error message saying that the key and secret can not be used in that state.

Cause

Admin App secret configuration and/or Azure SQL configuration values became corrupted for whatever reason.

Steps for Recovering the Application

1) Clear Configuration Parameters & Force Admin App's First-Time Setup

On this step, we need to clear all the data records created during first time setup.

Please make sure to stop ODS API and Admin App websites under IIS or within the Azure portal App Service.

Ex (in Azure): EdFiOdsApiWebSite-{environment}-{resourceGroupid}

EdFiOdsAdminAppWebSite-{environment}-{resourceGroupid}

2. Connect to SQL Server on SSMS or use Azure Query Editor

3. Select the EdFi_Admin database.

4. Execute the following sql commands for clearing all the data records created during first time setup process.

SQL

BEGIN TRAN   
DECLARE @ApplicationId INT;

SELECT @ApplicationId = ApplicationId FROM dbo.Applications WHERE ClaimSetName = 'Ed-Fi ODS Admin App'

DELETE FROM dbo.ClientAccessTokens WHERE EXISTS (
        SELECT 1 FROM dbo.ApiClients
        WHERE ClientAccessTokens.ApiClient_ApiClientId = ApiClients.ApiClientId
        AND Application_ApplicationId = @ApplicationId 
) 

    DELETE FROM dbo.ApiClients WHERE Application_ApplicationId = @ApplicationId
    DELETE FROM dbo.ApplicationEducationOrganizations WHERE Application_ApplicationId = @ApplicationId
    DELETE FROM dbo.ProfileApplications WHERE Application_ApplicationId = @ApplicationId
    DELETE FROM dbo.Applications WHERE ApplicationId = @ApplicationId
    DELETE FROM dbo.OdsInstances
    DELETE FROM adminapp.SecretConfigurations
COMMIT  TRAN

5. Once the SQL commands executed successfully. Please start the ODS API and Admin App websites under IIS or within the Azure portal App Service.

2) Update the Admin App Configuration Parameters

There is a table in the EdFi_Admin database called adminapp.AzureSqlConfigurations. This table holds the encrypted configuration parameters used by the admin app.

The format of this string is JSON and specifies a few key: value pairs.

Here is a template of how it looks: {"AdminCredentials":{"Password":"[dbpassword]","UserName":"[dbuser]"},"HostName":"[the SQL Server: sql.somthing.com]","ProductionApiCredentials":{"Password":"[SecurePassword]","UserName":"EdFiOdsProductionApi"},"AdminAppCredentials":{"Password":"[SecurePassword]","UserName":"EdFiOdsAdminApp"}}

The following JSON code block explains the parameters required and their intention:

SQL

{
	//These are the credentials used to access the EdFi_Admin database.
	"AdminCredentials":{ 
			"Password":"[dbpassword]",
			"UserName":"[dbuser]"
	},
	// This is the address of the MsSQL server. This can be a DNS or an IP Address.
	"HostName":"[the SQL Server: sql.somthing.com]", 
	// These are the credentials that will be stored encrypted that the Admin App will use to connect to the Ed-Fi ODS API
	"ProductionApiCredentials":{ 
			"Password":"[SecurePassword]",
			"UserName":"EdFiOdsProductionApi"
	},
	"AdminAppCredentials":{
			"Password":"[SecurePassword]",
			"UserName":"EdFiOdsAdminApp"
	}
}

Modify the SQL statement below by providing the User Name and Password for the required fields marked with square brakets "[...]"

Following the steps above open SSMS or Azure Query Editor and execute the following statement against the EdFi_Admin database.

SQL

BEGIN TRAN   
UPDATE adminapp.AzureSqlConfigurations set field='{"AdminCredentials":{"Password":"PW Specified in Deployment Script","UserName":"SERVER Master UN"},"HostName":"","ProductionApiCredentials":{"Password":"Enter PW","UserName":"EdFiOdsProductionApi"},"AdminAppCredentials":{"Password":"","UserName":"EdFiOdsAdminApp"}}' WHERE Id=1;
COMMIT  TRAN

3) Update Admin App web site on IIS or Azure

Note: That older versions of Admin app need the presence of “SetupRequired” file. This indicates to the first time setup process that it has not run. If the file not present, this means that the first-time setup was completed. Recreating the file will enforce the First time setup process to run again.

To create this file just create text file with the name “SetupRequired” and set the content of it to: Placeholder file to let the AdminApp know additional setup of the system is required.

On IIS or Azure, proceed to restart the application. Once the restart has finished use your web browser and navigate to the Admin App URL. You should be able to continue the First Time Setup within Admin App.

Deployed pages and resources can be accessed on Azure portal.

https://www.gslab.com/blogs/kudu-azure-web-app

References

If you have any questions on how to connect to the EdFi-Admin database please refer to this articles below:

https://docs.microsoft.com/en-us/azure/azure-sql/database/connect-query-portal

https://docs.microsoft.com/en-us/azure/azure-sql/database/connect-query-ssms

Resetting Admin App Configuration (Draft Update)

[data-colorid=wmdtnh7xpm]{color:#7b7c7d} html[data-color-mode=dark] [data-colorid=wmdtnh7xpm]{color:#828384}[data-colorid=wpt4uxytz8]{color:#7b7c7d} html[data-color-mode=dark] [data-colorid=wpt4uxytz8]{color:#828384}Environment: OnPrem

Admin App Version: >= 2.2.0

Steps for Recovering the Application on Shared Instance mode

1) Clear Configuration Parameters & Force Admin App's First-Time Setup

Environment: Azure

Admin App Version: < 2.2.0

Issues

Cause

Steps for Recovering the Application

1) Clear Configuration Parameters & Force Admin App's First-Time Setup

2) Update the Admin App Configuration Parameters

3) Update Admin App web site on IIS or Azure

References

Environment: OnPrem