External API call to create users?

[dfaulken]

We had discussed that on interview completion we would automate adding a user to umasstransit.org. Is that still something we want to do or are we keeping this app generic so that it could be adopted by other departments on campus?

Or, option 3, are we keeping it generic but this is something that most folks might want to do after completing an interview (so we could abstract out the API call into a configuration file or something)?

Any thoughts @sherson?

[werebus]

My suggestion would be an optional attribute (of the "department"?) that specifies an http callback URL to which we POST a standard, documented user payload if it's defined.

[sherson]

I like option 3, and @werebus' suggestion.

[werebus]

Of course, it's easy for me to say.

The hard part is actually authentication / authorization. If we open up an endpoint on umasstranst.org that allows POSTing of users, thats essentially account-creation.

We need to figure out some way to limit it to only authorized applications. OAuth? SSL Certificates? Some sort of secret token?

[dfaulken]

Hmm, and particularly how to make it configurable.

[dfaulken]

As an update, this will likely not be addressed for a couple of years, while we move towards the next implementation of our internal monolith app which stores employee records.