#11 Proxy credential mismatch with sgfac and ogce portlets
I noticed a bug within the sgfac and proxy-manager portlets, where if one had already obtained a proxy credential (via sgfac or proxy-manager), trying to log into the opposite portlet (sgfac or proxy-manager portlet) with your proxy information would lead to a crash. Basically, it seems that you can't have a proxy obtained from BOTH proxy-manager portlet and sgfac at the same time.
Here are a series of tests I performed, one can try these to reproduce the errors (after each test, I restarted the portal):
1) Log into OGCE portal. Next tried starting sgfac portlet using my myproxy credential information.
SUCCESSFUL
2) Log into OGCE portal. Next clicked on proxy-manager portlet and successfully obtained a credential. Then I clicked on sgfac portlet and entered my myproxy credential information in the form.
After filling the form and hitting submit, I received an error:
Could not connect to registry at https://156.56.104.14:6666/xregistry?wsdl please fix that by going to settings
Stacktrace for this error is attached.
3) Logged into OGCE portal. Next tried starting sgfac portlet using my myproxy credential information, successfully logged in. However, after successfully opening up sgfac portlet, I then tried clicking on the proxy-manager portlet tab and tried to obtain a myproxy certificate by filling out the required form. After clicking: "Get proxy from MyProxy", I received an error, and no proxies loaded as a result:
Error: MyProxy get failed. [Caused by: Authentication failed [Caused by: Failure unspecified at GSS-API level [Caused by: Bad certificate (The signature of 'C=US,O=National Center for Supercomputing Applications,CN=myproxy.teragrid.org' certificate does not match its issuer)]]]
Discussion
GFac proxy request error stacktrace.
Logged In: YES
user_id=1884621
Originator: YES
NOTE: After test #2, I once again performed test #1 successfully and had no problems running sgfac. This shows that the problems with test #2 and test #3 are unrelated.