JBE authentication alternatives
I am trying to run JBE on a box, but really dont want to use my Jazz password (as my company requires that it changes every 90 days).
Are there any other alternatives for authenticating the JBE client? OAuth would seem ideal, but I can't see how this would be possible... Does anyone have any ideas? (I am running Jazz 2.0) |
3 answers
On 2010/09/06 8:38, antonpiatek wrote:
I am trying to run JBE on a box, but really dont want to use my Jazz Assuming from you e-mail address that your company is IBM, then I suggest that you create a functional ID and configure it so its password never expires. Your manager may have to jump through a bunch of bureaucratic hoops to make it happen, but it is possible. If you can't manage a non-expiring password, is it so hard to change your password and restart the JBE every three months? If it's just one machine, that shouldn't be much of a burden (though it would be nice to not have to do it). If you have a build farm with about 50 build machines, like we do, then it becomes a major hassle. |
|
So there is no other way to have JBE authenticated? I was hoping something related to OAuth might be possible...
|
OAuth is not supported with JBE in 2.x or 3.0. In 3.0 we're adding support for authenticating with a stored certificate or via smartcard, but I don't think that would help your scenario.
If supporting multiple engines, you could use -passwordFile and point to a shared file. That way only the single password file would need to be updated when the password changes. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.