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

Integration Token Credential ID #272

Closed
idokaplan opened this issue Dec 19, 2016 · 11 comments
Closed

Integration Token Credential ID #272

idokaplan opened this issue Dec 19, 2016 · 11 comments

Comments

@idokaplan
Copy link

Hi,

I cannot choose "Credential ID".
The list is empty, but there are credentials that are configured.

Can you please advise?
Thanks!
Ido

@vinhtvu2
Copy link

Are they configured as "Secret Text" in the "Kind" field?

@fredpalmer
Copy link

@vinhtvu2 Open dev tools - I found that I couldn't get the credentials plugin to truly add the credentials via the build configuration page due to a Mixed Content issue:

https://issues.jenkins-ci.org/browse/JENKINS-35150

developer_tools_-_https___builds_artistgrowth_com_job_ag-nexus-webtest-build_configure

I think you can get around it by adding the credentials directly: <your-build-server>/credentials/store/system/domain/_/newCredentials

@jblaine
Copy link

jblaine commented Apr 19, 2017

This doesn't work for me either.

I tried version 2.2.

I configured a "Secret text" credential in my Jenkins folder (not from the job config page) as we do for all manner of other credentials and types just fine. When configuring a job there to try to use Slack, the secret text credential does not show as a choice in the drop-down, effectively making this plugin fully inoperable for us :(

@dsoprea
Copy link

dsoprea commented Apr 24, 2017

Bump. I'm having this issue, too.

@dsoprea
Copy link

dsoprea commented Apr 25, 2017

It looks like there's an issue with creating it as a non-admin user but then not being able to see it because you're a non-admin. It's a Jenkinsism.

@eagletmt
Copy link
Contributor

I also ran into this issue. I've created a PR to fix this #315

@Edwin-van-der-Klaauw
Copy link

This is a serious bug because I have to give all users system admin access rights to the entire Jenkins environment or else non-admin users saving one of the projects will silently break the link with Slack notifications leaving new build/test failures unnotified to the teams. This bug makes the whole plug-in useless. There seems to be something fundamentally wrong with access rights; How can you have NO READ access but do have WRITE (clear) access? Please fix!

@haidaraM
Copy link

No one seems to maintain this plugin anymore 😕

@timja
Copy link
Member

timja commented Dec 16, 2018

fix released in 2.4

@timja timja closed this as completed Dec 16, 2018
@rishabhjain05
Copy link

Hi, I am facing an issue with the credential's dropdown, it only shows "none" no matter how many times I have added the secret key. I also tried to reinstall the Slack notification plugin and also restart the Jenkins twice. But still facing the same issue.

@timja
Copy link
Member

timja commented Dec 22, 2020

Hi, I am facing an issue with the credential's dropdown, it only shows "none" no matter how many times I have added the secret key. I also tried to reinstall the Slack notification plugin and also restart the Jenkins twice. But still facing the same issue.

the scope needs to be set to global and of the "Secret text" type.

Please create a new issue and post a screenshot if it's still an issue after the above

@jenkinsci jenkinsci locked and limited conversation to collaborators Dec 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants