New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Authentication and Authorization Support to the ServiceControl REST API #400

Closed
fafachd opened this Issue Oct 24, 2014 · 9 comments

Comments

Projects
None yet
8 participants
@fafachd

fafachd commented Oct 24, 2014

(see Particular/ServicePulse#3 for background)

There needs to be a way to do authentication and authorization on the SC REST API so IT OPS can run ServiceInsight on their desktops without exposing the REST API to everyone on the network.
The alternative is to have IT Ops remote into the server, but in larger orgs this access is very difficult to obtain.

@wooliet

This comment has been minimized.

Show comment
Hide comment
@wooliet

wooliet Oct 28, 2014

+1
Gaining access to anything in a moderately sized org is almost universally a painful process (especially as an outside contractor). Their ability to keep the production server locked down while still granting access to the web service is critical.

wooliet commented Oct 28, 2014

+1
Gaining access to anything in a moderately sized org is almost universally a painful process (especially as an outside contractor). Their ability to keep the production server locked down while still granting access to the web service is critical.

@jarrettv

This comment has been minimized.

Show comment
Hide comment
@jarrettv

jarrettv commented Oct 28, 2014

+1 agree

@dewojcik

This comment has been minimized.

Show comment
Hide comment
@dewojcik

dewojcik Oct 28, 2014

+1 Totally the case here - this would be a great improvement.

dewojcik commented Oct 28, 2014

+1 Totally the case here - this would be a great improvement.

@rsutkowski

This comment has been minimized.

Show comment
Hide comment
@rsutkowski

rsutkowski Oct 29, 2014

WE NEED THIS!!!! Production servers are so locked down, nobody outside of the production control group has access nor will ever get access. PLEASE MAKE THIS A PRIORITY!

rsutkowski commented Oct 29, 2014

WE NEED THIS!!!! Production servers are so locked down, nobody outside of the production control group has access nor will ever get access. PLEASE MAKE THIS A PRIORITY!

@fafachd

This comment has been minimized.

Show comment
Hide comment
@fafachd

fafachd commented Feb 29, 2016

Any update on this, @johnsimons or @andreasohlund?

@johnsimons

This comment has been minimized.

Show comment
Hide comment
@johnsimons

johnsimons Feb 29, 2016

Contributor

No updates @fafachd, at the moment we are focusing on performance improvements.

@Particular/servicecontrol-maintainers should we raise this in plat dev ?

Contributor

johnsimons commented Feb 29, 2016

No updates @fafachd, at the moment we are focusing on performance improvements.

@Particular/servicecontrol-maintainers should we raise this in plat dev ?

@gbiellem

This comment has been minimized.

Show comment
Hide comment
@gbiellem

gbiellem Mar 1, 2016

Contributor

@johnsimons I'd say yes as it concerns multiple products.

Contributor

gbiellem commented Mar 1, 2016

@johnsimons I'd say yes as it concerns multiple products.

@johnsimons

This comment has been minimized.

Show comment
Hide comment
@johnsimons

johnsimons Mar 1, 2016

Contributor

This issue has been raised internally in plat dev.

@fafachd thanks a lot for starting this discussion, the way we manage this kind of suggestions, is by raising them internally in a private repo, where we prioritise it and manage it from now on.
So with that in mind, I'll close this suggestion for now, and once we are ready to act on it we will reopen it. This does not mean we will not be working on it.

Contributor

johnsimons commented Mar 1, 2016

This issue has been raised internally in plat dev.

@fafachd thanks a lot for starting this discussion, the way we manage this kind of suggestions, is by raising them internally in a private repo, where we prioritise it and manage it from now on.
So with that in mind, I'll close this suggestion for now, and once we are ready to act on it we will reopen it. This does not mean we will not be working on it.

@johnsimons johnsimons closed this Mar 1, 2016

@johnsimons johnsimons added Type: Discussion and removed Feature labels Mar 1, 2016

@fafachd

This comment has been minimized.

Show comment
Hide comment
@fafachd

fafachd commented Mar 2, 2016

Thanks, @johnsimons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment