Hello Craig,
In JBoss/Wildfly environment, you need to explicitly declare runtime dependencies. I
assume that you're deploying your provider via dropping the JAR into the
standalone/deployments dir. In this case, you need to have
META-INF/jboss-deployment-structure.xml like this:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="org.keycloak.keycloak-services" />
</dependencies>
</deployment>
</jboss-deployment-structure>
If you are deploying as a module, use "module add ...
--dependencies=org.keycloak.keycloak-services" jboss-cli command. It will auto-create
the proper XML module descriptor for you.
Cheers,
Dmitry
On Fri, 2019-02-01 at 16:36 -0600, Craig Setera wrote:
In addition to my question yesterday about REST endpoint extensions,
I now
have a new issue. Basically, my hope/plan was to create a REST endpoint
and use that to retrieve a new type of action token that I was
implementing. I was able to create a new REST endpoint and validate that
the incoming user has the authority we want to require to initiate the new
action.
Now, I'm trying to create the new action token to be returned. I've
implemented all of the necessary interfaces. However, it is failing to
deploy properly because all of the required classes are part of the
keycloak-services module which appears to not be accessible. Am I missing
something here? How can I create a new action token implementation and get
it properly deployed and working?
Thanks,
Craig
=================================
*Craig Setera*
*Chief Technology Officer*
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user