cred_list in the proxy plugins should add group credentials first and append global later
Begin forwarded message:
From: Parag Mhashilkar
Subject: Re: ProxyFirst vs ProxyAll question
Date: February 24, 2016 at 1:49:04 PM CST
To: Brian Bockelman
Cc: "Fajardo Hernandez, Edgar" , GlideinWMS Support
Sorry, missed this email. It got filtered out before I saw it.
It turns out that it won’t work that way. When proxy list is created, global proxies are added first and group specific one later. So even if the group’s plugin type ‘ProxyFirst’ over rides global ‘ProxyAll’ correctly, the plugin will always select ProxyA today. If we have to keep the notion of scoping, I can see this being a bit inconsistent.
We can make the proxy list population to add group proxies before global proxies to address this. But for now, your best bet is to define credentials specific to each group and avoid global credentials in case you have groups that will only need a certain set of credentials.
On Feb 24, 2016, at 12:53 PM, Brian Bockelman wrote:
Catching up on old emails - did this get resolved?
On Feb 17, 2016, at 11:37 AM, Fajardo Hernandez, Edgar wrote:
Dear Gwms Experts,
I have a question for u folks. I have a fronted with one proxy defined in the credentials in the “general” section (lets call it proxyA) with plugin ProxyAll. And in a couple of the FE groups another proxy (proxy B). If I change the plugin in these groups to ProxyFirst, will the glide ins from this proxy only use the proxyB, or would they be using both?
My question is if I have on proxy defined in the general section. How can I enforce another (one and only proxy) in some of the subgroups?
#2 Updated by HyunWoo Kim almost 4 years ago
- Status changed from New to Feedback
- Assignee changed from HyunWoo Kim to Parag Mhashilkar
I think I found the solution.
I modified one line in glideinFrontendConfig.py
then I tested and confirmed that the credential in group is picked up when group is using ProxyFirst and there is another credential in the global section.