SQL Profile Provider Error "Procedure of function sp_UpdateUserProfile expects parameter @FirstName"

Follow

SecureAuth Idp Version affected: All

Description:

When using SQL to store some of the Profile entries for a user, the following error occurs

SqlProfileProvider.SetPropertyValues: Error received when saving data to user storage, exception: Procedure or function 'sp_UpdateUserProfile' expects parameter '@FirstName', which was not supplied.

sqlfirst.PNG
Cause:

The Standard SQL Stored Procedures included in older documentation expects a value for all attributes. This isn't a problem when using SQL as the complete profile store but when only using it for a few attributes, if these values are missing, it throws an error


Resolution:

Please proceed with caution. If you're unfamiliar with SQL, it would be better to contact our Tailoring team so they can customise the SQL stored procedures for your needs. These instructions are provided as an example only, SecureAuth does not provide support for issues that arise from improper usage of SQL Server Management Studio. Always take a backup.

1. Open SQL Management Studio

2. Expand "UserStore" (Default name for SecureAuth SQL DB)

3. Expand Programmability | Stored Procedures

4. Right click on dbo.sp_UpdateUserProfile and select Modify

5. Append = '' to the end of each variable that does not already have a default value. See screenshot for example of how this will look. 

6. Click Execute to save the change.

 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

 

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

 

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.