ghengeveld/atlassian-crowd-client

Node.js API & Client for Atlassian Crowd REST API

Hi, I'm Gert 👋

I'm a full stack software engineer trying to improve the world of frontend development through Component Driven Development and better workflows around it. I work for Chromatic and contribute to Storybook. I also built React Async.

Follow me on Twitter.

atlassian-crowd-client's Issues

Username not included in Crowd Session?

Looking at the Crowd documentation, it seems that session.validate includes a username:

{
    "expand": "user",
    "token": "abc123",
    "user": {
        "name": "sampleuser"
    },
    "link": {
        "href": "https://crowdserver/crowd/session/abcc123",
        "rel": "self"
    },
    "created-date": 1464453000000,
    "expiry-date": 1464456600000
}

But this is never parsed into the Session object: https://github.com/ghengeveld/atlassian-crowd-client/blob/master/src/models/session.js#L17

Is there any specific reason for being it done like this? can it be added?

crowd.user.get(username, true) does not work after last update

Basing on the error mesage,

I checked the file : models/attributes.js ---> attributesArr.forEach
attributesArr is NOT an array so that do NOT have forEach function.

I print out attributesArr, it is an object, NOT an array.

cannot authenticate with atlassian-crowd-client

I new in this and I get the error of Error: Invalid Response from Crowd, expecting JSON.
should I change something? here is my code:

var crowd = new atlassianCrowdClient({
  baseUrl: 'http://account.tikab.org/crowd/console/login.action',
  application: {
    name: 'test-app',
    password: 'AbC123456'
  }
});
crowd.session.create('[email protected]', 'Aa123456')
    .then(function (session) {
      console.log('Crowd SSO token is ' + session.token);
    })
    .catch(function(err) {
        console.log('err' + err)
    })

session.getuser not returning expirydate (expiresAt) along with the user detail

New usermanagement endpoint in Crowd 3.3

There is a new endpoint coming with Crowd 3.3 (/rest/usermanagement/1/authentication/notify). Will this be supported anytime soon? I would happy to create a pull request to get this feature working.

Docs