8000 Okta expand apiKeys · Issue #624 · stormpath/express-stormpath · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Dec 13, 2018. It is now read-only.
This repository was archived by the owner on Dec 13, 2018. It is now read-only.
Okta expand apiKeys #624
Open
Open
@babadofar

Description

@babadofar

Hi, I'm trying to migrate a Stormpath application that relied heavily on using api keys, and was relieved to see that you had implemented a solution for this on top of Okta. However, I see a bug when trying to call Account. getApiKeys -> apiKeys are not populated.

Is this something you intend to support going forwards? I find the migrated apikeys now in customdata. In the mean time I will just read them from there.

This can be easily tested using the express-stormpath-sample-project, and initing stormpath like this:

app.use(stormpath.init(app, {
  expand: {
    customData: true,
    apiKeys: true
    
  }
}));

Code breaks here: https://github.com/stormpath/stormpath-sdk-node/blob/1.0.0-rc5/lib/resource/Account.js#L447

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0