Dive into a comprehensive live-coding session where experts from Okta and Spring collaborate to make the Okta Spring Boot starter compatible with Spring Native. Learn how to troubleshoot and resolve issues related to GraalVM integration, including fixing configuration classes, adding resource and type hints, and creating a Hints JAR. Follow along as the team demonstrates the Okta CLI, discusses build times on different architectures, and explores tools like SDKMAN and SmartSynchronize. Gain insights into Maven quirks, Spring Init, and best practices for developing with Spring Native and Okta's authentication services.
Spring Native with Okta Spring Boot Starter - Implementation and Troubleshooting
Overview
Syllabus
- Introductions
- The point of today
- Reproducing the problem
- Fixing the code in OktaOAuth2AutoConfig
- Add proxyBeanMethods = false to @Configuration annotation
- Who's running the Maven commands?
- Why doesn't Maven auto-reload pom.xml anymore?
- Has anyone compared native build times on M1 vs Intel?
- A brief introduction to Spring Init
- MissingResourceException: Resource bundle not found
- Add a @ResourceHint annotation
- SDKMAN only holds on to the last couple Java versions
- FileNotFoundException: class path resource does not exist
- Add @TypeHint for conditional classes
- Same FileNotFoundException, try adding the parent class and AccessBits.ALL
- Create Hints JAR while we're waiting
- We got it working!!
- Testing with the Hints JAR - FileNotFoundException
- Brian Demers: This is about the time I break down...
- Brian Demers: What is this fuzzy thing?
- Okta CLI Demo
- Brian Demers: Choco?
- SmartSynchronize to the rescue!
- Add @ResourceHints to the Hints JAR
- Brian Demers: Pay your developers!
- It works with external hints!
Taught by
Okta
