How do I fix a import issue related to auth.idp.oidc.OidcAdapterConfig?

william.victorio · January 21, 2026, 2:33pm

Im trying to import this lib

import com.inductiveautomation.ignition.gateway.auth.idp.oidc.OidcAdapterConfig;

but its not working.

I already tried adding the dependencies into the build.gradle, and I added these lines into the module.xml file

<depends module-id="com.inductiveautomation.oidc" scope="G"/>
<depends scope="G">com.inductiveautomation.openid-connect</depends>

I’m using this lib to create a Identity provider via code, automatically. Can someone help me figure this out or maybe tell me another way to do it? Thank you.

Kevin.Herron · January 21, 2026, 2:40pm

This isn't a class that I see even exists in 8.1 or 8.3.

Are you trying to build a module? Are these module.xml things you tried just insane hallucinations from an LLM?

william.victorio · January 21, 2026, 2:45pm

Yes this is a module I’m trying to build, and yep I tried chat gpt and it said for me to add those things into module.xml. Completely madness adding that to module.xml?

paul-griffith · January 21, 2026, 4:51pm

If you're using Gradle, you should be using our module plugin, which automatically generates a module xml based on the attributes declared in code, e.g.

github.com/inductiveautomation/ignition-sdk-examples

perspective-component/build.gradle.kts

92813eb6e


      
          ignitionModule {
              // name of the .modl file to build
              fileName.set("RadComponents")
          
              // module xml configuration
              name.set("RadComponents")
              id.set("org.fakester.radcomponent")
              moduleVersion.set("${project.version}")
              moduleDescription.set("A module that adds components to the Perspective module.")
              requiredIgnitionVersion.set("8.3.0")
              license.set("license.html")
          
              // If we depend on other module being loaded/available, then we specify IDs of the module we depend on,
              // and specify the Ignition Scope that applies. "G" for gateway, "D" for designer, "C" for VISION client
              // (this module does not run in the scope of a Vision client, so we don't need a "C" entry here)
              moduleDependencies.put("com.inductiveautomation.perspective", "DG")
          
              // map of 'Gradle Project Path' to Ignition Scope in which the project is relevant.  This is is combined with
              // the dependency declarations within the subproject's build.gradle.kts in order to determine which
              // dependencies need to be bundled with the module and added to the module.xml.

This file has been truncated. show original

The dependency declarations that are generated are 1:1 with Ignition module IDs.
There is no com.inductiveautomation.oidc nor com.inductiveautomation.openid-connect module.

All IdP related functionality Ignition currently supports is embedded in the platform, meaning you don't have to declare any module dependency to use it. Whether we export anything useful to you is another question, but in general I would say to trust your LLMs a lot less than you currently are.

william.victorio · January 21, 2026, 6:03pm

Thank you guys very much, I’ll follow your steps. LLMs told me a completely different thing.…thats why I came here into the forum to ask the experts. Thanks!