Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In this way, your enhancer will be applied as the last link of the Enhancer Chain, before building the final JWT token.

Build the JAR

Lightweight JAR

You will use this method when NOT using external dependencies that Spring Boot does not bring

For the Identity Manager to use the plugin, you’ll need to package the project into a JAR file, either with mvn clean install or mvn clean package

...

Please note that whatever the repository is, the file needs to be public, as the Identity Manager will try to download it without any kind of authentication.

FAT JAR

You will use this method whenever you DO use external dependencies that does not come with Spring Boot

The process is slightly different. In this case you’ll want to add the maven assembly plugin to your pom.xml

Code Block
<build>
	<plugins>
		<plugin>
			<artifactId>maven-assembly-plugin</artifactId>
			<configuration>
				<descriptorRefs>
					<descriptorRef>jar-with-dependencies</descriptorRef>
				</descriptorRefs>
			</configuration>
			<executions>
				<execution>
					<id>make-assembly</id> 
					<phase>package</phase> 
					<goals>
						<goal>single</goal>
					</goals>
				</execution>
			</executions>
		</plugin>
	</plugins>
</build>

Then you’ll generate your plugin with mvn package

Keep in mind that this will generate a JAR with all dependencies, and therefore considerably increase the size of the plugin.

Define the URI of the plugin in the Identity Manager (Oauth Server)

...