Bug 1068104 - Reload of external configuration file for IDP doesn't work
Summary: Reload of external configuration file for IDP doesn't work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: PicketLink
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: DR2
: EAP 6.3.0
Assignee: Anil Saldhana
QA Contact: FIlip Bogyai
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-21 12:38 UTC by FIlip Bogyai
Modified: 2015-12-01 05:53 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-28 15:42:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker PLINK-356 0 Major Resolved Reloading configuration in IDP doesn't work 2016-02-03 08:24:46 UTC

Description FIlip Bogyai 2014-02-21 12:38:47 UTC
Description of problem:
Configuration file picketlink.xml can be referenced outside of war deployment, with time interval to reload this configuration. When Identity Provider(IDP) initialize this external configuration on start up, you can make any changes in its configuration file, but they won't be applied. I have tested it for changes in <KeyProvider> configuration (try to add or remove ValidatingAlias for some SP and identity federation is working without change).
For Service Provider(SP) the reload functionality works fine.

How reproducible:
Start IDP with no configured SP. Then add ValidatingAlias for SP in configuration file and wait until next reload. If you try to access this SP the identity federation is not working. 

This configuration I have used in jboss-web.xml:
<vault>
  <class-name>org.picketlink.identity.federation.bindings.tomcat.idp.IDPWebBrowserSSOValve</class-name>
  <param>
    <param-name>timerInterval</param-name>
    <param-value>5000</param-value>
  </param>
  <param>
    <param-name>configFile</param-name>
    <param-value>/path-to/picketlink.xml</param-value>
  </param>
</vault>

Comment 1 JBoss JIRA Server 2014-02-25 23:42:44 UTC
Anil Saldhana <anil.saldhana> updated the status of jira PLINK-356 to Resolved

Comment 2 FIlip Bogyai 2014-03-06 11:29:46 UTC
Issue was fixed in Picketlink 2.5.3.Final, verified in EAP 6.3.0.DR2


Note You need to log in before you can comment on or make changes to this bug.