Closed mraible closed 3 years ago
I'm guessing we should detect dependencies in the pom (or gradle build) 🤔
Maybe one of the following dependencies?
It might be easier to look at package.json
for JHipster. If it's a regular JHipster app, it'll have generator-jhipster
as a dev dependency. If it's a blueprint, it'll have generator-jhipster-{blueprint-name}
. For example, https://github.com/oktadeveloper/okta-jhipster-micronaut-example/blob/master/package.json#L95.
Perfect!, we could probably start out with basic string matching.
There are a few different backends now right? Spring, Micronaut, and something for .net?)
Yes, there are a few different backend options now:
I haven't tested each of them to see if they work with Okta, but they should all have OIDC support.
Fixed by #83.
The JHipster option with Okta CLI expects you to be using Spring Boot. That won't always be the case since there's also Node.js, Quarkus, .NET, and Micronaut versions of JHipster. Ideally, our Okta CLI is smart enough to detect the framework used and override the appropriate environment variables. In this case, you could look for
generator-jhipster-micronaut
in the dependencies.When I tried
okta apps create
on this repo and selected JHipster, it writes the following to.okta.env
:Ideally, for Micronaut, it'd write: