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
We are trying to upgrade to keycloak 17.0.1 quarkus distribution, but we have some old provide is using Jakarta EE API (e.g jboss-ejb-api_3.2_spec) but related code is not working like throwing
Error in creating PasswordHashProvider: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or in an application resource file: java.naming.factory.initial
If that is not supported, may i know any work around or solution to migrate such provide? As we need hibernate jtp in our provide to access another data source.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
We are trying to upgrade to keycloak 17.0.1 quarkus distribution, but we have some old provide is using Jakarta EE API (e.g jboss-ejb-api_3.2_spec) but related code is not working like throwing
Error in creating PasswordHashProvider: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or in an application resource file: java.naming.factory.initialMay i konw if those API is not supported afterward? As i see the document still mention we can do that:
https://www.keycloak.org/docs/latest/server_development/#leveraging-jakarta-ee
If that is not supported, may i know any work around or solution to migrate such provide? As we need hibernate jtp in our provide to access another data source.
Beta Was this translation helpful? Give feedback.
All reactions