getAccounts() is unimplemented on Okta branch for OktaApplication, OktaTenant and OktaDirectory

[george-hawkins-work]

OktaApplication.getAccounts() and much of the rest of the Application public interface methods throw UnsupportedOperationException. This is true also of OktaTenant and OktaDirectory.

This despite the Okta release of the Spring Boot SDK being marked a release candidate (RC3 actually).

We deliberately left off migrating to Okta as we wanted to wait until the Spring Boot SDK migration was more mature. But time is pressing now - we assumed the release candidates would be near-finished versions - this lack of methods allowing us to query things like accounts is extremely worrying for us!

Is there an easy way to access this information in some kind of Okta specific fashion? I'm guessing not, otherwise why not wire the Stormpath methods through to this logic 😞

If we look at the Github active branches page for the SDK we see that there's been relatively little development against this repo recently (no checkins in the last 11 days).

This gives the disturbing impression that team Stormpath has maybe already packed up and turned off the lights. Sorry if some of you are working super hard to make this work but you can understand our worries as the August deadline approaches.

[bdemers]

@george-hawkins-aa The Okta branch/release of this project only supports the integrations (Spring, Spring-Boot, and Servlet)

Please contact support@stormpath.com and we can help you figure out the best plan for your use cases.

[george-hawkins-work]

Hello @bdemers - the term "integrations" clearly means something definite to people within Stormpath but even after reading the FAQ I can't say I have a clear idea what it means.

If I use the Okta branch of the Stormpath Spring Boot SDK it is not the case that the Stormpath specific classes like Account etc. have gone away and that I now have to e.g. stick to pure Spring Security interfaces.

So Stormpath specific classes like Account, Group etc. continue to be useable much as before while implementations of interfaces like Application etc., while continuing to exist, throw UnsupportedOperationException for most things.

So what exactly is the demarkation point? What part of the Stompath world continues to exist and what is now out-of-bounds? I.e. could you more clearly explain what "integrations" means in terms of the Stormpath Java SDK API?

My impression is that anything that involves logging in as an individual still works as before but querying the system for higher level groups, e.g. all users, is not. For this functionality it seems we have to fallback to Okta's own Java SDK.

I wrote a small gist on my experience toda working with this SDK in combination with the Stormpath SDK. But I can't be the first person doing this - are there already migration documents covering this end of things?