Hi!
I miss couple of things in the design of JBoss Federated SSO.
As I understand, browser sends the SAML based token to each application that participated in SSO.
1) When the SAML based token is added to browser? After the authentication of a user?
2) How the token is added to browsers? Which browsers support today storing of the SAML based token?
3) How the token is sends to an HTTP client? As an HTTP parameter? As an HTTP header? Something else?
I will appreciate any explanation.
Best regards,
Michael
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204566#4204566
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204566
"remy.maucherat(a)jboss.com" wrote :
| Normally, the web tier embedded in AS uses VFS for almost everything
| already (it has a DirContext-over-VFS implementation),
|
As it seems direct VFS is not enough,
we need whole VDF, with its mutable VFSDeploymentUnit (VDU).
Like my code suggests, one would add an 'external' metadata location,
containing custom resources (in JBP's case their custom .tld),
and once web tier would do a lookup for those resources,
it would go over VDU's metadata locations, not really caring where they come from.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204551#4204551
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204551
"remy.maucherat(a)jboss.com" wrote :
| Normally, the web tier embedded in AS uses VFS for almost everything
| already (it has a DirContext-over-VFS implementation), but indeed TLD
| may use some work. It should be pluggable for Catalina (it only uses it
| to lookup for listeners), but for Jasper it's harder. I sort of hoped
| nobody would notice ... So I suppose some review is needed.
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204550#4204550
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204550
WRT:
- http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203370#4203370
- http://www.jboss.com/index.html?module=bb&op=viewtopic&t=149197
How hard would it be to 'move'/impl JBossWeb's TLD lookup based on MC's VDF?
My use case for JBossPortal (JBP) would be:
1) recognize that deployment is JBP app
2) add JBP's custom TLD to VFSDeploymentUnit's metadata locations
e.g.
| VirtualFile customJbpTLDs = VFS.getRoot(".../jboss-portal/config/tlds");
| unit.appendMetaDataLocation(customJbpTLDs);
|
3) JBossWeb would understand VDF (VFSDeploymentUnit - VDU)
and do a tld lookup based on VDU's metadata locations
This would mean if we run in an environment that uses VDF
we should first try to look for metadata via VDF
only then fall back to plain resources lookup.
This way the services that use VDF won't have to introduce
hacks to add custom metadata - like JBP does it currently.
btw: where exactly does .tld file lookup happen?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204549#4204549
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204549
That sounds great, thanks!
Getting you access to the project source repository is a two step process. First you need to sign the online contributor agreement, which will get routed to me or Mark for approval. Once that's done I'll ask our IT people to make the necessary permission changes on the svn server.
Meanwhile you could create a JIRA issue against the JBossTransactions (JBTM) project and submit the code by attaching it to the issue and I'll take it from there.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204529#4204529
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204529