sunxacml-announce Mailing List for Sun's XACML Implementation
Brought to you by:
farrukh_najmi,
sethp
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Seth P. <set...@su...> - 2004-07-16 22:54:50
|
I'm pleased to announce that the 1.2 release of SunXACML is now ready for download. The web pages have been updated to point to the latest programmer's guide and javadocs too. This release doesn't map to a new release of the XACML specification, but it does represent a number of new features, some of which people have been requesting for a long time. Download the latest package, take it for a spin, and let me know what you think! With the 1.2 release finished, I'll now be turning my sights on a 2.0 release to support the new XACML 2.0 specification (which should be ready soon). This will involve a lot of work, and so I'm looking for people to join the effort. A few brave souls have already been in touch, but if you're interested, send me some email and we can chat. seth |
From: Seth P. <set...@su...> - 2004-06-09 22:20:17
|
Amazing but true, the long-awaited 1.2 package has finally hit release candidate status. Over the next few weeks I'll be working on new examples, documentation, and web pages. I'll also be listening for comments, suggestions, and bug reports. That's where you come in. Go grab the code from the CVS tree, either through annonymous CVS access or by downloading the nightly tarball [1] at http://cvs.sourceforge.net/cvstarballs/sunxacml-cvsroot.tar.bz2 Take it for a spin and let me know what you discover. With a very few (sadly necessary) exceptions, no APIs have been removed or modified (though some have been deprecated) so it should be fairly easy to try the new code with any existing projects. What's changed, you ask? Why, all kinds of good stuff! At a high level... New Features: - All factories are now pluggable, and the base functionality exists in convenience classes so it's easy to write your own implementations - There's a new ConfigurationStore class that provides run-time configuration for PDPs and factories, and a flexible XML schema for defining the configurations - A new tests module in the root of the CVS tree provides a basic package for running the standard conformance tests against the code - All function classes are now public and constructable, and a new cluster interface makes it easy to get a bundle of similar functions - Basic logging has been added to most of the core code so you can track some of the more interesting events Specific changes and re-factorings: - EvaluationCtx is now an interface, so you can define your own context behavior, and a PDP can be queried directly with a context - All collections' mutability is handled consistently and safely - The resource-id is always included in a Result - ResourceFinders now get the context when queried for hierarchies - 5 fixes from the 1.1 release, including correct handling for namespaces in XPath expressions Of course, there are lots of other changes in there, but that should get you excited enough for now :) seth [1] you probably want to wait until tomorrow for this, since it won't get updated until later tonight |
From: Seth P. <set...@su...> - 2004-03-09 15:51:53
|
I posted about this a while ago, but since several people recently have asked, here's a clarification.. Yes, there is a bug in the 1.1 release for Obligations encoding. The Obligation tags don't get wrapped in a single Obligations tag. That was fixed shortly after the release, and if you grab the current CVS tree you'll get the fix. Also, the obligation.xml sample policy contains multiple Obligations tags, which is incorrect. It should contain only a single Obligations tag. This will be fixed in the next version. Changing subjects.. I'm working on features for a 1.2 release. These will include run-time configuration, better error reporting, improved interfaces [1], etc. If there's a feature that you particularly want to see, please let me know in the next few weeks so I can try to get it in...and if there's a feature that you would like to work on, that's even better! seth [1] I'm doing my best not to break any interfaces. So far, I've been successful, so any code written to the 1.1 release will work with the 1.2 release. Just wanted to let you know in case you were getting worked up :) |
From: Seth P. <set...@su...> - 2003-11-08 23:57:00
|
I'm very pleased to announce the 1.1 release of the SunXACML project. The new release includes all the latest code and docs, and also includes a number of sample programs and policy examples to help you out. Go grab this new release and let us know what you think! seth |
From: Seth P. <set...@su...> - 2003-08-29 19:46:55
|
The CVS tree has been tagged as v1_1_rc1. This represents release candidate 1 of the 1.1 version of this project. There's a lot of new stuff in there since the 1.0 release, including support for XACML 1.1, new APIs, some bug fixes, and a host of documentation updates. If you've been holding off on grabbing a recent version of the code, I suggest that you wait no longer. What happens now? Over the next few weeks the code will be carefully reviewed and tested [1], the programmer's guide will be updated to reflect the new functionality, and several new examples and samples will be included. Once this is done, a final 1.1 version of the code will be packaged and made available on our project page. We hope that you will send in comments or problems you have with the latest code, since many of the new features are direct results of feature requests. Feel free to start discussion threads on the sunxacml-discuss list. Enjoy! seth [1] The code has been well tested, and is believed to be very stable, but many new features are in there. The bottom line is that you should feel confident at this point moving from the 1.0 build to this latest version. |
From: Seth P. <set...@su...> - 2003-07-22 21:41:58
|
The latest CVS tree has two notable updates that I thought people might find interesting: 1. a small bug fix for AttributeValue encoding (thought this went in a while ago, but apparently I was wrong as someone hit up against this bug). 2. a change in the constructors for RequestCtx so they now use a Subject class rather than a Set of Lists. The second item in particular has been a common request, so I suspect that if you're writing code that generates Requests you'll want to grab the latest bits. I think it's pretty self-evident how the new interface works, but let me know if you have any problems. seth |
From: Seth P. <Seth.Proctor@Sun.COM> - 2003-06-26 02:31:19
|
Ok, a few things to announce: 1. The -devl list is now setup so anyone can subscribe to it. You still won't be able to post unless you're a developer on this project, but it will make it easier to lurk. 2. There have been a few recent improvements to the source, and in the next few weeks I expect to see some more code & documentation changes, which I hope will mean that we get a new packaged release put together soon. 3. There is a lead article on java.sun.com today. Woo-hoo! Go tell all your friends :) I suspect that this will bring new people to this project, so if you're reading this message after just discovering this project, welcome! That's about it for now. Hope things are going well for everyone. seth |
From: Seth P. <set...@su...> - 2003-06-16 15:57:27
|
another test seth |
From: Seth P. <set...@su...> - 2003-06-16 15:55:46
|
testing this new list... seth |