Tag: authentication
-
Jenkins CI: my account password did not work any more, but I found a way to fix it
Q: how to solve this? A: mostly by taking notes Q: which security model do I use? A: “Role-Based Strategy“ general approach: fix a few bits within config.xml and another few bits within your Jenkins web GUI for editing config.xml stop your Jenkins of course create a new (privileged) user account, and change your main…
-
my Jenkins “automation” server at home uses the “Role Strategy Plugin”
https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin Without this plugin there wasn’t really any security, because everybody (even w/o user account) could see jobs and their build log files – and certain log files contain sensitive details. My Jenkins guru Nathan pointed me to this plugin.
-
there is an Jenkins automation server meant to be “for registered users only” — but everybody can inspect the build logs
Its security setting looks like this: “Security Realm”=>”Jenkins’ own user database” My question: Is there a way to impose even more restrictions, e.g.: before authentication you seen nothing You need the “role strategy” plugin for achieving this.
-
the JIRA REST API, how to authenticate, …
https://en.wikipedia.org/wiki/Jira_(software) https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-basic-authentication https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-cookie-based-authentication https://metacpan.org/module/json_pp – a nice utility, that also does JSON pretty-printing; it comes with http://search.cpan.org/perldoc?JSON There are certainly legion of reasons to use a REST API and also to use the JIRA REST API, I wanted to create a linear “diary” of JIRA actions. This is our sample JIRA issue URL: http://kelpie9:8081/browse/QA-31 This is its…