You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by rene-d-menoto <gi...@git.apache.org> on 2016/10/13 12:46:25 UTC
[GitHub] wicket pull request #183: Page instantiation protection by combined ruleset.
GitHub user rene-d-menoto opened a pull request:
https://github.com/apache/wicket/pull/183
Page instantiation protection by combined ruleset.
There is currently no way to annotate a page with instantiation rules on
multiple roles. It is possible to use an AuthorizeInstantiation. But
this can only roles using an OR ruleset.
With this annotation in use we are able to combine multiple OR rulesets
in an AND relation.
Example:
A page can be instantiate only by users with ADMIN and DATABASE role.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rene-d-menoto/wicket wicket-7.x
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/wicket/pull/183.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #183
----
commit 0093eee4d747dddc469e1368e18e661c621e7ba5
Author: Ren� Dieckmann <gi...@menoto.de>
Date: 2016-10-13T12:23:40Z
Page instantiation protection by combined ruleset.
There is currently no way to annotate a page with instantiation rules on
multiple roles. It is possible to use an AuthorizeInstantiation. But
this can only roles using an OR ruleset.
With this annotation in use we are able to combine multiple OR rulesets
in an AND relation.
Example:
A page can be instantiate only by users with ADMIN and DATABASE role.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] wicket pull request #183: Page instantiation protection by combined ruleset.
Posted by rene-d-menoto <gi...@git.apache.org>.
Github user rene-d-menoto closed the pull request at:
https://github.com/apache/wicket/pull/183
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] wicket issue #183: Page instantiation protection by combined ruleset.
Posted by rene-d-menoto <gi...@git.apache.org>.
Github user rene-d-menoto commented on the issue:
https://github.com/apache/wicket/pull/183
Thanks for merging.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] wicket issue #183: Page instantiation protection by combined ruleset.
Posted by martin-g <gi...@git.apache.org>.
Github user martin-g commented on the issue:
https://github.com/apache/wicket/pull/183
Created a ticket: https://issues.apache.org/jira/browse/WICKET-6265
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] wicket issue #183: Page instantiation protection by combined ruleset.
Posted by martin-g <gi...@git.apache.org>.
Github user martin-g commented on the issue:
https://github.com/apache/wicket/pull/183
I've cherry picked this commit and applied it at `wicket-7.x` with https://git1-us-west.apache.org/repos/asf?p=wicket.git;a=commit;h=14b922cd.
Git merge/rebase leads to too much noise in the commits@ mailing list.
@rene-d-menoto Thank you for the contribution! Please close this PR!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---