Is anyone testing it? If yes, please let me know or create a jira at AGSEC for testing. I'd like to release it this afternoon. Bruno Oliveira wrote: > Good morning everyone, > > I'm planning to release AeroGear Security 1.0.1 on this Wednesday or at > maximum Thursday morning. For this reason: AG Security, AG Security > PicketLink and AG Security Shiro were staged under > https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... . > > > You can also take a look at our example here: > https://github.com/aerogear/aerogear-controller-demo/pull/63. > > A complete list of JIRAs solved in this release: > > - AGSEC > > https://issues.jboss.org/issues/?jql=project%20%3D%20AGSEC%20AND%20fixVer... > > > - AGJS > > https://issues.jboss.org/browse/AGJS-3 > > Changelog > > - AeroGear Security > > * Merge branch 'AGSEC-63' > * Updates on README > * Javadoc updates > * License headers, please > * R.I.P AeroGearUser > * Refactoring to generics > * Code clean up > * Make it more decoupled > * Code clean up > * Bump up to snapshots > * Merge branch 'travis' > * enable notifications > * Minimal configuration for travis > > - AeroGear Security PicketLink > > * Merge branch 'AGSEC-63' > * Removal of old note > * Removing old references to AeroGearUser > * Updates at Javadocs > * License headers, please > * R.I.P AeroGearUser > * Make the implementation compatible with AGSEC > * Living on the edge with PicketLink beta4 > * Accept generic entities > * Refactoring and clean up to be compatible with the new release > * Merge branch 'AGSEC-56' > * Inclusion of snapshot repositories > * Code clean up > * Upgrade to PicketLink 2.5 beta3 > * Merge branch 'travis' > * enable notifications > * Minimal configuration for travis > > - AeroGear Security Shiro > > * A little bit of Javadoc > * Travis configuration file > * R.I.P AeroGearUser > * License headers, please > * Update to be compatible with the latest changes on AGSEC > * Readme instructions > * Fixing compilation issues > * Unit testing grant configuration > * Inclusion of unit tests just for the sake of my sanity > * Inclusion of TODO > * Import clean up > * Inclusion of support to secrets > * Extracting methods to Identity management implementation > * Inclusion of authentication validation > * Inclusion of methods for grant > * Addition of .gitignore > * User registration > * Initial support for Shiro > > - AeroGear Controller Demo app > > * Inclusion of staging repository > * Fixing persistence issues > * R.I.P AeroGearUser > * Updating the demo to keep the compatibility with AGSEC > > Feedback is always welcome. > -- abstractj _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

I've just migrated an scaffolded app with the latest staging release. After some refactoring I had no issues (just issues that are related specific to my app) Just wondering why the signature of login has changed (User, Password) instead of just (User) On Thu, Jun 13, 2013 at 2:33 PM, Bruno Oliveira <bruno(a)abstractj.org&gt;wrote: > Is anyone testing it? If yes, please let me know or create a jira at > AGSEC for testing. > > I'd like to release it this afternoon. > > Bruno Oliveira wrote: > > Good morning everyone, > > > > I'm planning to release AeroGear Security 1.0.1 on this Wednesday or at > > maximum Thursday morning. For this reason: AG Security, AG Security > > PicketLink and AG Security Shiro were staged under > > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... > . > > > > > > You can also take a look at our example here: > > https://github.com/aerogear/aerogear-controller-demo/pull/63. > > > > A complete list of JIRAs solved in this release: > > > > - AGSEC > > > > > https://issues.jboss.org/issues/?jql=project%20%3D%20AGSEC%20AND%20fixVer... > > > > > > - AGJS > > > > https://issues.jboss.org/browse/AGJS-3 > > > > Changelog > > > > - AeroGear Security > > > > * Merge branch 'AGSEC-63' > > * Updates on README > > * Javadoc updates > > * License headers, please > > * R.I.P AeroGearUser > > * Refactoring to generics > > * Code clean up > > * Make it more decoupled > > * Code clean up > > * Bump up to snapshots > > * Merge branch 'travis' > > * enable notifications > > * Minimal configuration for travis > > > > - AeroGear Security PicketLink > > > > * Merge branch 'AGSEC-63' > > * Removal of old note > > * Removing old references to AeroGearUser > > * Updates at Javadocs > > * License headers, please > > * R.I.P AeroGearUser > > * Make the implementation compatible with AGSEC > > * Living on the edge with PicketLink beta4 > > * Accept generic entities > > * Refactoring and clean up to be compatible with the new release > > * Merge branch 'AGSEC-56' > > * Inclusion of snapshot repositories > > * Code clean up > > * Upgrade to PicketLink 2.5 beta3 > > * Merge branch 'travis' > > * enable notifications > > * Minimal configuration for travis > > > > - AeroGear Security Shiro > > > > * A little bit of Javadoc > > * Travis configuration file > > * R.I.P AeroGearUser > > * License headers, please > > * Update to be compatible with the latest changes on AGSEC > > * Readme instructions > > * Fixing compilation issues > > * Unit testing grant configuration > > * Inclusion of unit tests just for the sake of my sanity > > * Inclusion of TODO > > * Import clean up > > * Inclusion of support to secrets > > * Extracting methods to Identity management implementation > > * Inclusion of authentication validation > > * Inclusion of methods for grant > > * Addition of .gitignore > > * User registration > > * Initial support for Shiro > > > > - AeroGear Controller Demo app > > > > * Inclusion of staging repository > > * Fixing persistence issues > > * R.I.P AeroGearUser > > * Updating the demo to keep the compatibility with AGSEC > > > > Feedback is always welcome. > > > > -- > abstractj > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Because we don't have the attribute "Password" on User interface (from PL). One solution would be implement or extend SimpleUser

, but I don't want AeroGearUser back.

Sebastien Blanc wrote: > I've just migrated an scaffolded app with the latest staging release. > After some refactoring I had no issues (just issues that are related > specific to my app) > Just wondering why the signature of login has changed (User, Password) > instead of just (User) > > > On Thu, Jun 13, 2013 at 2:33 PM, Bruno Oliveira <bruno(a)abstractj.org > <mailto:bruno@abstractj.org>> wrote: > > Is anyone testing it? If yes, please let me know or create a jira at > AGSEC for testing. > > I'd like to release it this afternoon. > > Bruno Oliveira wrote: > > Good morning everyone, > > > > I'm planning to release AeroGear Security 1.0.1 on this Wednesday > or at > > maximum Thursday morning. For this reason: AG Security, AG Security > > PicketLink and AG Security Shiro were staged under > > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... . > > > > > > You can also take a look at our example here: > > https://github.com/aerogear/aerogear-controller-demo/pull/63. > > > > A complete list of JIRAs solved in this release: > > > > - AGSEC > > > > > https://issues.jboss.org/issues/?jql=project%20%3D%20AGSEC%20AND%20fixVer... > > > > > > - AGJS > > > > https://issues.jboss.org/browse/AGJS-3 > > > > Changelog > > > > - AeroGear Security > > > > * Merge branch 'AGSEC-63' > > * Updates on README > > * Javadoc updates > > * License headers, please > > * R.I.P AeroGearUser > > * Refactoring to generics > > * Code clean up > > * Make it more decoupled > > * Code clean up > > * Bump up to snapshots > > * Merge branch 'travis' > > * enable notifications > > * Minimal configuration for travis > > > > - AeroGear Security PicketLink > > > > * Merge branch 'AGSEC-63' > > * Removal of old note > > * Removing old references to AeroGearUser > > * Updates at Javadocs > > * License headers, please > > * R.I.P AeroGearUser > > * Make the implementation compatible with AGSEC > > * Living on the edge with PicketLink beta4 > > * Accept generic entities > > * Refactoring and clean up to be compatible with the new release > > * Merge branch 'AGSEC-56' > > * Inclusion of snapshot repositories > > * Code clean up > > * Upgrade to PicketLink 2.5 beta3 > > * Merge branch 'travis' > > * enable notifications > > * Minimal configuration for travis > > > > - AeroGear Security Shiro > > > > * A little bit of Javadoc > > * Travis configuration file > > * R.I.P AeroGearUser > > * License headers, please > > * Update to be compatible with the latest changes on AGSEC > > * Readme instructions > > * Fixing compilation issues > > * Unit testing grant configuration > > * Inclusion of unit tests just for the sake of my sanity > > * Inclusion of TODO > > * Import clean up > > * Inclusion of support to secrets > > * Extracting methods to Identity management implementation > > * Inclusion of authentication validation > > * Inclusion of methods for grant > > * Addition of .gitignore > > * User registration > > * Initial support for Shiro > > > > - AeroGear Controller Demo app > > > > * Inclusion of staging repository > > * Fixing persistence issues > > * R.I.P AeroGearUser > > * Updating the demo to keep the compatibility with AGSEC > > > > Feedback is always welcome. > > > > -- > abstractj > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- abstractj _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On Thu, Jun 13, 2013 at 10:44:48AM -0300, Bruno Oliveira wrote: > Because we don't have the attribute "Password" on User interface (from > PL). One solution would be implement or extend SimpleUser, but I don't > want AeroGearUser back. The problem with this is since this changes a public API, it stops being a point release :( I wouldn't oppose to bump this to 1.1.0, though.