Skip to content
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

VSTS Extension - Widget Service Endpoint Access #4673

Closed
shaunmarx opened this issue Jun 25, 2018 · 2 comments
Closed

VSTS Extension - Widget Service Endpoint Access #4673

shaunmarx opened this issue Jun 25, 2018 · 2 comments
Assignees
Labels
action/investigate feature/vsts kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time size/medium ~1 week

Comments

@shaunmarx
Copy link

In order for the VSTS widgets to work the user must be added to the service endpoint Users group. We should investigate whether we can allow an admin user to configure the widget to use a separate access token as an alternative in order to use those endpoints alleviating the need to add all users to the given service endpoint group.

Original Source: https://help.octopus.com/t/web-deploy-gives-a-powershell-error-after-upgrade-to-latest-version/20128/47

@shaunmarx shaunmarx added kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time feature/vsts labels Jun 25, 2018
@droyad droyad added the size/medium ~1 week label May 13, 2019
@droyad droyad self-assigned this May 13, 2019
@droyad
Copy link
Contributor

droyad commented May 21, 2019

There has not been much demand for this and is unlikely to reach the top of our TODO list. If you would like to see this feature, comment below.

@droyad droyad closed this as completed May 21, 2019
@droyad droyad assigned droyad and unassigned droyad May 21, 2019
@lock
Copy link

lock bot commented Aug 19, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action/investigate feature/vsts kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time size/medium ~1 week
Projects
None yet
Development

No branches or pull requests

2 participants