OK. It looks like we can have multiple usages of the JSON ticket
registry : from a simple one to a more advanced one.
Would you mind creating a JIRA to track that request for 4.1 ?
Sure, https://issues.jasig.org/browse/CAS-1369.
Pax,
M
--
You are currently subscribed to cas-dev@lists.jasig.org
Hi,
OK. It looks like we can have multiple usages of the JSON ticket registry :
from a simple one to a more advanced one.
Would you mind creating a JIRA to track that request for 4.1 ?
Thanks.
Best regards,
Jérôme
2013/10/9 Marvin S. Addison
> I think it makes sense as JSON has become a widel
I think it makes sense as JSON has become a widely adopted standard. We
should certainly wait for 4.1 though.
That timeline seems reasonable.
At first, I thought you were talking about the Unicon extension :
https://github.com/Unicon/cas-addons/wiki/Configuring%20JSON%20Service%20Registry.
It
Hi,
I think it makes sense as JSON has become a widely adopted standard. We
should certainly wait for 4.1 though.
At first, I thought you were talking about the Unicon extension :
https://github.com/Unicon/cas-addons/wiki/Configuring%20JSON%20Service%20Registry
.
It seems to be the same idea, isn'
I'm curious whether there's any interest in contributing our JSON
service registry to the official CAS project.
https://gist.github.com/serac/6886509
It's a fairly simple component with a notable capability: support for
file storage on shared volumes such as NFS. We use this component to
back
