This repository has been archived by the owner on Dec 13, 2018. It is now read-only.
Cannot read property getGroups of undefined #579
Assignees
Comments
the-overengineer
pushed a commit
that referenced
this issue
Jan 31, 2017
- The dependency stormpath-config handles the configuration helpers that are used by the SDK. - This update is necessary as there is an update within the EnrichIntegrationFromRemoteConfigStrategy file which sets the client on the outerScope object. Without this the calls to getGroups wil yield undefined. This was resolved with this commit: stormpath/stormpath-node-config@4946166 closes #579
hueter
pushed a commit
to emsiengineering/express-stormpath
that referenced
this issue
Apr 6, 2017
* add missing parenthesis to user data example * Updating Sphinx theme. * Update stormpath config dependency - The dependency stormpath-config handles the configuration helpers that are used by the SDK. - This update is necessary as there is an update within the EnrichIntegrationFromRemoteConfigStrategy file which sets the client on the outerScope object. Without this the calls to getGroups wil yield undefined. This was resolved with this commit: stormpath/stormpath-node-config@4946166 closes stormpath#579 * Release 3.1.9 See docs/changelog.rst * Fix issue with adding custom required fields when registering user * Fix minor issue with validation error text * Add test for failing custom data validation * Fix error message check in test * wip * cleanup and test update * fix Authorization header typo * Add backcompat for req.accessToken * fix spacing * refactor * Log the error message from the authenticator This error message now has useful information about they the token validation failed * upgrade to stormpath@0.20.0 * deprecate loginRequired, give better 401 message from authenticationRequired * Re-write the authentication section to cover all the cases * initial multi tenancy support * tweaks according to feedback from @robert * remove caching and let that be handled on the SDK layer * Remove name key from the login form when not needed This fixes all but one of the failing tests * stub new set of tests * fix description of fixture * Sync with Robert's code * Update helpers and controllers to pass existing tests * Update email verification tests so that they work * Apply verification to forgot password flow controllers * Fix behaviour for redirect with query params * Use two applications in fixtures * Fix bug with application cleanup * Make autoLogin work on register * Cleanup, WIP on email reset * Implement fixes so that all tests pass * Fix style issue * Simplify org expansion condition in register * Sprinkling documentation and cleaning up * Fixing bugs * Docs fixes * Fix unrelated test that was failing * Rename helper * Allow user to define their own organization resolver * Document latest changes * Fixes and improvements: * Updated yml file with latest from framework spec * Most of the flows were not supplying the resolved organization context as the `accountStore` option, I’ve fixed this. * The login form was not using the computed view model, which is required in order to render the form fields properly (they were rendering without name properties) * Removing the access token path, we decided to remove any authorization checks from this first version. This first version only resolves organization context by subdomain. * Cleanup of test case, you can manually supply a Host header to the request() calls * Add and test check if org is mapped to app * Add CachedStore helper class * Document Cached Store * Place CachedStore in getFormViewModel and defaultOrgResolver middleware * Fix issue with circular dependencies * Clarify naming * Fix: show “org not found” error if org not mapped, while on org selection form Before this fix you would be redirected to the same form, but without an error * Assert that custom orgResolver is used * Add the organization name to other forms, if present * Multi-tenancy documentation * Added more info about the /idSiteResult endpoint * Updated phrasing to make sense Thanks @robert! * Release 3.2.0 See docs/changelog.rst * Docs: remove usage of loginRequired, use authenticationRequired * add a test for custom data on root of object * Okta Announcement Readme Update * Updating the readme with migration information
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Essentially we need to update
stormpath-configto0.0.27but currently its at0.0.26. Maybe consider always updating the patch versions if the plan is to follow semver?I'll make a PR shortly.
Links to:
stormpath/stormpath-sdk-node#596
The text was updated successfully, but these errors were encountered: