sqlserver database error

[yangyuditest]

Describe the bug

When using SQL Server, the JdbcOAuth2AuthorizationService throws an error:
"The string is not in a valid hex format"

Root Cause

SQL Server does NOT support BLOB type (2004).
It only supports VARBINARY(MAX) which maps to JDBC type -3 (Types.VARBINARY).

But in the mapping code:

(Types.BLOB == columnMetadata.getDataType()

It only checks for BLOB(2004), not VARBINARY(-3).
So SQL Server binary fields get STRING values instead of byte[] → hex format error.
Expected behavior
The framework should support SQL Server by checking Types.VARBINARY(-3) in addition to Types.BLOB(2004).
Fix code suggestion
Change:
Types.BLOB → Types.VARBINARY
Or support both:
(Types.BLOB == type || Types.VARBINARY == type)
Environment
Spring Authorization Server version: 1.5.6  或 spring-security-oauth2-authorization-server
Database: SQL Server
Table schema: VARBINARY(MAX) for token fields
Error message: The string is not in a valid hex format

[kaicoder-dev]

This same error appears with Oracle database as well when using blob.

[Yashwanthvarma283]

Hi, I’d like to work on this issue.

From the description, it seems the problem is due to only checking Types.BLOB while SQL Server (and Oracle) use VARBINARY for binary data.

I’ll investigate the JDBC type handling and propose a fix that supports both types.

Please let me know if this approach works.