Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[higgins-dev] Proper home for card generator code

Before committing Andy's updates to the card generator code, we wanted to make sure it's going into the correct project.
 
Right now it's in the STS core, though it's neither consuming nor being consumed by STS components.  We were thinking there may be use cases where one wants to deploy a card generator which is not co-located with the STS.
 
If the card generator is required to use the same key for signing as the STS uses to sign token responses, then it seems like we'd need it co-located with the STS.
 
Here are some other points made by Mike:
 
(10:30:47 AM) mgmcintosh: I think there are common config elements
(10:31:07 AM) mgmcintosh: the key and issuer and mex uri are bound to the sts
(10:31:38 AM) mgmcintosh: also think the image is something that the STS will want to config
(10:32:17 AM) mgmcintosh: I think the same key is supposed to sign the card as the key used to sign RSTRs - but not 100% sure
(10:34:55 AM) mgmcintosh: I think when deploying the STS I will want to deploy the card gen ui - at least for default installs - so I will probably want the UI to be in the same WAR
 
 

Back to the top