Mailing-List: contact user-help@shiro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@shiro.apache.org
MIME-Version: 1.0
In-Reply-To: <1469568289679-7581177.post@n2.nabble.com>
References: <1469555309532-7581171.post@n2.nabble.com> <CAH9eYVpEdMRWwmPh503n3jWAQsyO2wz1HF821uCjP-qMTt3sdw@mail.gmail.com>
 <1469558964911-7581173.post@n2.nabble.com> <CAH9eYVpHpv0FDwo3CpU3whZZJadCa=T-NtAwQEPyPZJ1Q78zHQ@mail.gmail.com>
 <1469563320544-7581175.post@n2.nabble.com> <CAH9eYVrVRVu5=3Lh__Hq6OD6fCW-SiO-yeV-0csiEPsQ=Tu_AA@mail.gmail.com>
 <1469568289679-7581177.post@n2.nabble.com>
From: Brian Demers <brian.demers@gmail.com>
Date: Tue, 26 Jul 2016 22:27:28 -0400
Message-ID: <CAH9eYVofoWHTq7aykgU8Bjomj3S9y5ozjbj9_kUMS4iaQd3SQA@mail.gmail.com>
Subject: Re: Principal added by AuthorizingRealm
To: "user@shiro.apache.org" <user@shiro.apache.org>
Content-Type: multipart/alternative; boundary=001a114d957e432d33053894c237
archived-at: Wed, 27 Jul 2016 02:27:37 -0000

--001a114d957e432d33053894c237
Content-Type: text/plain; charset=UTF-8

The list wouldn't need to be static, you could query it from your db, or
other source.  It is just that generating the list would be done outside of
Shiro initially.

On Tue, Jul 26, 2016 at 5:24 PM, jonathan.labin <jonathan.labin@gmail.com>
wrote:

> A good suggestion.
> In practical terms, this would probably work just fine.  I'd prefer to
> allow
> for new roles to be defined (as different combinations of existing
> permissions)  order without needing to change the application code.
>
> But I could see how that could work if I could guarantee  that the roles
> were fixed.
>
>
>
> --
> View this message in context:
> http://shiro-user.582556.n2.nabble.com/Principal-added-by-AuthorizingRealm-tp7581171p7581177.html
> Sent from the Shiro User mailing list archive at Nabble.com.
>

--001a114d957e432d33053894c237
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The list wouldn&#39;t need to be static, you could query i=
t from your db, or other source.=C2=A0 It is just that generating the list =
would be done outside of Shiro initially.</div><div class=3D"gmail_extra"><=
br><div class=3D"gmail_quote">On Tue, Jul 26, 2016 at 5:24 PM, jonathan.lab=
in <span dir=3D"ltr">&lt;<a href=3D"mailto:jonathan.labin@gmail.com" target=
=3D"_blank">jonathan.labin@gmail.com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">A good suggestion.<br>
In practical terms, this would probably work just fine.=C2=A0 I&#39;d prefe=
r to allow<br>
for new roles to be defined (as different combinations of existing<br>
permissions)=C2=A0 order without needing to change the application code.<br=
>
<br>
But I could see how that could work if I could guarantee=C2=A0 that the rol=
es<br>
were fixed.<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://shiro-user.582556.n2.nabble=
.com/Principal-added-by-AuthorizingRealm-tp7581171p7581177.html" rel=3D"nor=
eferrer" target=3D"_blank">http://shiro-user.582556.n2.nabble.com/Principal=
-added-by-AuthorizingRealm-tp7581171p7581177.html</a><br>
<div class=3D"HOEnZb"><div class=3D"h5">Sent from the Shiro User mailing li=
st archive at Nabble.com.<br>
</div></div></blockquote></div><br></div>

--001a114d957e432d33053894c237--