stormpath-sdk-java
stormpath-sdk-java copied to clipboard
stormpath
Official Java SDK for the Stormpath User Management REST API
With the move to 1.0.2 an `AuthenticationSuccessEvent` is no longer published when a successful login occurs. Previously I believe the Spring Security `ProviderManager` used to iterate through all the authentication...
I've only observed this with the Client API, but I was told that this is a Java SDK bug. When I send a `POST` to the `/forgot` endpoint, I get...
When an existing cache configuration exists and Stormpath caches are not configured, startup fails with: ``` Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'stormpathApplication' defined in class path resource...
https://stormpath.atlassian.net/wiki/display/AM/Account+Linking
http://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html#boot-features-external-config-typesafe-configuration-properties Doing this would allow others to inject our configuration into a Spring-managed class, rather than relying on individual `Value` annotations. Those would still work of course, but `ConfigurationProperties` is...
The [Node.js docs](https://docs.stormpath.com/nodejs/express/latest/configuration.html) use: ``` export STORMPATH_CLIENT_APIKEY_ID=YOUR_ID_HERE export STORMPATH_CLIENT_APIKEY_SECRET=YOUR_SECRET_HERE export STORMPATH_APPLICATION_HREF=YOUR_APP_HREF ``` While we support: ``` STORMPATH_API_KEY_ID STORMPATH_API_KEY_SECRET ``` We should support `STORMPATH_CLIENT_APIKEY_ID` according to https://github.com/stormpath/stormpath-sdk-spec/blob/master/specifications/config.md I think this needs...
The 401 challenge for the `/me` endpoint differs between servlet and spring-mvc integrations For Spring-MVC the 401 is set directly from the [MeController](https://github.com/stormpath/stormpath-sdk-java/blob/e39caa66bbcfbdd1e9a127b828d22b4dddf1ca8d/extensions/servlet/src/main/java/com/stormpath/sdk/servlet/mvc/MeController.java#L100-L112) This causes a few problems: 1. If...
When we introduced `Organizations` our `DefaultAccountStoreMapping` disappeared. Now we have `DefaultApplicationAccountStoreMapping` and `DefaultOrganizationAccountStoreMapping`. This causes the following code to fail: `client.instantiate(AccountStoreMapping.class)`. It was working previously since we had a `DefaultAccountStoreMapping`...
It is not context relative currently, so if the web-app is deployed under a non-root context path (e.g. `/foo`), then redirects will fail. The workaround is to change various stormpath.web.*.nextUri...
