New oauth requests after updating to 2.0.0.2
Ok,
This weekend I updated an RTC repository to 2.0.0.2 from
1.0 (I20090618-1753) / 2.0 (I20090618-1753)
I ran the repoTools -addTables before winding up the repository for the first
time. This repo has a peer RQM project that is giving errors dealing with oauth. Looking at both repo oauth there is a new request (not yet trusted)
net.jazz.ajax.service.internal.http.ThemingHandler b9e913606a734724b486cc79203c28e6 Untrusted
Safe to trust ?
This weekend I updated an RTC repository to 2.0.0.2 from
1.0 (I20090618-1753) / 2.0 (I20090618-1753)
I ran the repoTools -addTables before winding up the repository for the first
time. This repo has a peer RQM project that is giving errors dealing with oauth. Looking at both repo oauth there is a new request (not yet trusted)
net.jazz.ajax.service.internal.http.ThemingHandler b9e913606a734724b486cc79203c28e6 Untrusted
Safe to trust ?
2 answers
Yes, it is safe for you to trust this consumer key. This consumer key will be used to enable theming of the Web UI if you choose to do so. If you are not using Web UI theming, then there shouldn't be any harm to other functionality either way.
However, I think there might be a small bug here. I believe that the APIs we use to create that consumer key should make it trusted automatically. I have filed the following work item to track this issue: https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=104645
Thanks,
Matt Jarvis
Jazz Foundation Developer
However, I think there might be a small bug here. I believe that the APIs we use to create that consumer key should make it trusted automatically. I have filed the following work item to track this issue: https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=104645
Thanks,
Matt Jarvis
Jazz Foundation Developer
Matt,
Thanks. I stepped into trusting on one server but it wanted an ID/password. We're a strict ldap shop with 90 day password lifetime.
:-(
Thanks. I stepped into trusting on one server but it wanted an ID/password. We're a strict ldap shop with 90 day password lifetime.
:-(
Yes, it is safe for you to trust this consumer key. This consumer key will be used to enable theming of the Web UI if you choose to do so. If you are not using Web UI theming, then there shouldn't be any harm to other functionality either way.
However, I think there might be a small bug here. I believe that the APIs we use to create that consumer key should make it trusted automatically. I have filed the following work item to track this issue: https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=104645
Thanks,
Matt Jarvis
Jazz Foundation Developer