On Tue, Dec 26, 2017 at 8:12 AM, Alceu R. de Freitas Jr.
wrote:
> Hello Coty,
> For the sake of others readers, I confirm the behavior you identified from
> SELinux:
Great, thanks.
> [root@localhost audit]# grep -P '^type=AVC' audit.log | grep name_bind
> type=AVC msg=audit(1513876523.918:145)
On 02/01/18 00:51, Robert J. Carr wrote:
> I'm looking to use some kind of combined realm where I can authenticate
> (and authorize) users both using the built-in login-config and externally
> using oauth. Ideally, in both cases, I'd be able to have access to roles,
> but this isn't a necessity.
>
On 02/01/18 09:50, Harrie Robins wrote:
> I'm still having problems with matching my pattern.
>
> Right now I'm feeding the following to internalProxies:
>
> ^103\\.21\\.(2(4[4-7]))\\.([0-9]|[1-9][0-9]|1([0-9][0-9])|2([0-4][0-9]|5[0-5]))$|^103\\.22\\.(2(0[0-3]))\\.([0-9]|[1-9][0-9]|1([0-9][0-9])
On 28/12/17 10:06, Olaf Kock wrote:
>
> On 27.12.2017 23:16, Eric Robinson wrote:
>>> I mean A is java8 and tomcat8.. so make a C that is tomcat6 and java8
>> I don't think so. This is a requirement of the software company whose
>> application solution we use. They are requiring us to move to tomc
I'm still having problems with matching my pattern.
Right now I'm feeding the following to internalProxies:
^103\\.21\\.(2(4[4-7]))\\.([0-9]|[1-9][0-9]|1([0-9][0-9])|2([0-4][0-9]|5[0-5]))$|^103\\.22\\.(2(0[0-3]))\\.([0-9]|[1-9][0-9]|1([0-9][0-9])|2([0-4][0-9]|5[0-5]))$
I created a list of all in
