Custom authentication module not visible after restart

This topic has 5 replies, 2 voices, and was last updated 4 years, 1 month ago by Andy Cory.

  • Author
    Posts
  • #22427
     hhakroush
    Participant

    Hi all, I’ve created a custom authentication module that matches my needs, created a jar file and copied it to /path/to/tomcat/webapps/openam/WEB-INF/lib/ , restarted tomcat and I still can’t see the custom authentication under Authentication/Modules.
    Any help? something I’m missing maybe?
    I’m using Access Management 6.0

    #22431
     Andy Cory
    Participant

    Did you also do the steps to add the auth module as a service, and register it? Putting your jar file into the right place isn’t enough on its own.

    -Andy

    #22434
     hhakroush
    Participant

    you mean using ssoadm? but the documents say that starting AM 5.5 a simple restart should do the trick.
    If not, can you please clarify how can i register the auth module as a service and register it?
    Thanks!

    #22438
     Andy Cory
    Participant

    Where are you looking in the docs? Looking at AM6 dev guide , I see it says:

    Installing the sample authentication module consists of copying the .jar file to AM’s WEB-INF/lib/ directory, registering the module with AM, and then restarting AM or the web application container where it runs.

    Copy, register, then restart. However, the steps below that text are missing info about how to register the module, that’s true. I did hear something about auto registration of modules coming in AM5.5, but AM6 docs do still mention registering the module.

    If registration is still required, look at the create-svc and register-auth-module subcommands for ssoadm.

    -Andy

    #22441
     hhakroush
    Participant

    but installing a custom authentication from the market works without registering anything, however the custom authentication module that we created for 13.0 isn’t working (not visible) on AM 6.0, what is the reason behind this?

    Thanks,
    Hosam

    • This reply was modified 4 years, 1 month ago by hhakroush.
    #22443
     Andy Cory
    Participant

    Hi Hosam

    I’m not able to answer that one I’m afraid. I’ve not yet looked at auto registration of auth modules on AM5.5+ – it was news to me that it was supported, to be honest! It might be worth checking the AM debug logs on message level when you start the container in case something is written there. Or the container logs themselves, maybe.

    -Andy

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.

©2022 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?