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
Currently, the hybrid model is exclusive for LDAP and Couchbase. A new feature in the ORM layer allows alias support for SQL to separate mappings.
Hence if the user-specified RDBMS the hybrid model should take into account the alias support rather than just the cross of Couchbase and LDAP.
Sample of jans-hybrid.properties when persistence type is hybrid and of type SQL.
The above snippet means that cache tokens, and sessions are in a separate database in SQL. This also means two conf property files will be needed, jans-sql.properties and jans-sql.token.properties.
This is very similar to couchbases mapping. Instead of CN_SQL_DB_NAME we should probably use a prefix style CN_SQL_DB_NAME_PREFIX
The text was updated successfully, but these errors were encountered:
The above snippet means that cache tokens, and sessions are in a separate database in SQL. This also means two conf property files will be needed, jans-sql.properties and jans-sql.token.properties.
This is very similar to couchbases mapping. Instead of CN_SQL_DB_NAME we should probably use a prefix style CN_SQL_DB_NAME_PREFIX
This would be tracked in separate GH issue (if feature is really still needed).
Currently, the hybrid model is exclusive for LDAP and Couchbase. A new feature in the ORM layer allows alias support for SQL to separate mappings.
Hence if the user-specified RDBMS the hybrid model should take into account the alias support rather than just the cross of Couchbase and LDAP.
Sample of
jans-hybrid.properties
when persistence type ishybrid
and of type SQL.The above snippet means that cache tokens, and sessions are in a separate database in SQL. This also means two conf property files will be needed,
jans-sql.properties
andjans-sql.token.properties
.This is very similar to couchbases mapping. Instead of
CN_SQL_DB_NAME
we should probably use a prefix styleCN_SQL_DB_NAME_PREFIX
The text was updated successfully, but these errors were encountered: