Community-driven, open-source software for user authentication, user identity management, and single-sign-on.
The opendj bug is documented here:
I am facing the same issue on one project.
We will probably talk about this later today here.
@nynymike @pavelhoral Looks like the fix for that issue is included in both our
master branch and our 3.5 branch. For master, search for OPENDJ-2969 in this listing: https://github.com/WrenSecurity/wrends/commits/053e00fd901
3.5 is harder to track down because we don't have the commit history, just the source; but if FR's bugster is to be trusted (it usually is) then they shipped a fix for this issue in 3.5 and we have 3.5, so I assume we have it there too
My status for this week is that I'd like to finally get DS 3.5.x builds with Wren branding off my plate :) If @martincizek can help me out with the logo changes requested in November (either through the designer or by sending me the PSDs) I can handle that.
Not sure if you guys have a common place for files like this over at Orchitech? Was wondering if maybe Martin stashed them somewhere you guys can access
In other news, I'm working with a client that is interested in using OpenIG. I dusted off our copy of IG and worked on getting it to build but there are some test failures related to Mockito upgrades that will need some attention. Basically the tests are checking that an object is an instance of a specific type; it's failing because it's a CGLib mock instead.
Yeah, we did. I don't remember running into this class cast issue before. Most of the issues we had in the other projects were that
assertThat() takes an overload for Future now, in addition to assertThat(T), so it was ambiguous at compile time. I was able to resolve that; this runtime issue feels new
anyList -> any or something like that
@siepkes or @pavelhoral I have a PR for fixing the JAX-RPC GPG sigs, if one of you can take a look: WrenSecurity/jax-rpc-ri#3
in wrenam, we (my crew) need to exclude query strings from policy url evaluation. Is there any method without write a custom authorization module ?
we need to protect many applications, which urls can contains several "?" character and it's very difficult define resource policy for everyone.
Our question is:
It's possible define a policy resource that evaluate only the base url ignoring the query string ?
I hope you understood ... my english isn't not so perfect.
*://*:*/*?*
*://*:*/*?*?*?*
Hm, RFC allows that - https://tools.ietf.org/html/rfc3986#section-3.4. So that might be a bug.
sorry ... somthing incomplete ...
To encode the '?' it's necessary an apache before the actual architecture because the AM agent intercepts calls the before all. We would avoid this.
Your example match exactly with our problem ... doesn't match!!!
I have created issue WrenSecurity/wrenam#44 . Unfortunatelly I need to work on a different project right now, but maybe someone else will pick it up from there.
hi wrens!
FYI, the wrensecurity.org domain expires on 2019-06-01:
Domain Name: WRENSECURITY.ORG
Registry Domain ID: D402200000002592295-LROR
Registrar WHOIS Server: whois.regtons.com
Registrar URL: http://subreg.cz
Updated Date: 2018-05-29T13:03:59Z
Creation Date: 2017-06-01T15:04:05Z
Registry Expiry Date: 2019-06-01T15:04:05Z
Registrar Registration Expiration Date:
Registrar: Gransy s.r.o.
Registrar IANA ID: 1505
Registrar Abuse Contact Email: abuse@regtons.com
Registrar Abuse Contact Phone: +420.734463373
Reseller:
Domain Status: ok https://icann.org/epp#ok
Registrant Organization: Whois protection, this company does not own this domain name s.r.o.
Registrant State/Province:
Registrant Country: CZ
Name Server: NS.GRANSY.COM
Name Server: NS2.GRANSY.COM
Name Server: NS4.GRANSY.COM
Name Server: NS3.GRANSY.COM
Name Server: NS5.GRANSY.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-05-24T09:10:25Z <<<
cc @pavelhoral