[
https://issues.apache.org/jira/browse/AIRAVATA-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Jayasekara resolved AIRAVATA-855.
---------------------------------------
Resolution: Fixed
I am resolving this as the primary concern is resolved. I am going to see point
3 after Raman attaches logs. If it is a issue I will create a separate Jira for
that.
Thanks
Amila
> Error retrieving credentials for community user.gateway - nulltoken id -
> null - Warning message
> ------------------------------------------------------------------------------------------------
>
> Key: AIRAVATA-855
> URL: https://issues.apache.org/jira/browse/AIRAVATA-855
> Project: Airavata
> Issue Type: Bug
> Components: GFac, Security
> Affects Versions: 0.8
> Reporter: Raminderjeet Singh
> Assignee: Amila Jayasekara
>
> I am getting " Error retrieving credentials for community user.gateway -
> nulltoken id - null" warning message multiple times for a single job running
> in Airavata. My job works fine but this warning messages is logged multiple
> time to the catalina.out.
> I have 3 concerns regarding this message:
> 1. Why we are calling credential store multiple times for a single request?
> We should call it one from GFAC API or Airavata API and pass the credential
> to required places. We can use SecurityContext in GFAC to shared it with
> handlers and providers.
> 2. As we have both the options to use credential store and property file (in
> current version), we need not to show the warning all the time. We should
> make this configurable by some flag. This is really important for GFAC unit
> test cases to pass without any warning message.
> 3. Cause of the warning is misleading "Caused by:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'us3airavata.credentials' doesn't exist". I already have the table but not
> the credential but the error is misleading.
> I will attach the log file for more information.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
