>-----Original Message----- >From: Ciancetta, Jesse E. >Sent: Tuesday, November 22, 2011 2:24 PM >To: shindig >Subject: RE: SecurityTokenKeyFile > >>-----Original Message----- >>From: daviesd [mailto:davi...@oclc.org] >>Sent: Tuesday, November 22, 2011 2:14 PM >>To: shindig >>Subject: SecurityTokenKeyFile >> >>I know there was a change recently (SHINDIG-1636) that changed the way >the >>token encryption key was loaded. I use to have >> >>"gadgets.securityTokenKeyFile" : "res://tokenkey.txt" > >Hmm -- I believe this should have worked and I tested this case when I was >testing the recent changes you referred to locally. I'll give it another try >in a >few minutes and report back what I find...
Actually -- sorry -- that wouldn't have worked. The property name changed to just gadgets.securityTokenKey as you mentioned below but now that one property can be configured using either the key directly, a resource reference or a file-system reference. The default container.js should have samples of the three different ways it can be used now -- so for loading from the classpath it should be: "gadgets.securityTokenKey" : "res:// tokenkey.txt ", That actually applies to any property in container.js now -- not just the security token key (the ability to pull the value from a classpath resource or file-system reference that is). Please let me know if this resolves the issue for you. > >> >>But this appears to be broken now. tokenkey.txt would be in the root of my >>classes directory. I was able to get this to work by providing the key >>directly >> >>"gadgets.securityTokenKey" : "xxxxxxxxxx=" >> >>What is the correct way to refer to the file now? >> >>Doug
