Community-driven, open-source software for user authentication, user identity management, and single-sign-on.
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
Hi to everyone :)
I have an issue during the build of WrenAM.
I clone the branch wrenam-sustaining-13.5.x
but I have this error:
I have an issue during the build of WrenAM.
I clone the branch wrenam-sustaining-13.5.x
but I have this error:
And this error
Can someone help me?
Also I don't understand why your maven tries to download AM dependencies from your custom (possibly mirror-of central) nexus repo. Those dependencies are in jfrog repo.
Can I have the jfrog url repos?
It ask me for the auth if I point to:
https://stash.forgerock.org/projects/OPENAM/repos/openam-sustaining/browse
https://stash.forgerock.org/projects/OPENAM/repos/openam-sustaining/browse
Not sure what you mean... you have to clone the project from GitHub (https://github.com/WrenSecurity/wrenam.git), then switch to branch sustaining/13.5.x and mvn package or install it with JDK 8 (I don't think the build works with 11)
JFrog (maven) repo should work out of the box as that is what is configured inside pom.xml.
The certificate is pretty fresh there (one week).
The SSL certificate on wrensecurity.org expired on 8/20
My browser won't let me navigate there :-)
My browser won't let me navigate there :-)
I hope Wren Security is still active.
Using the "Open Identity Platform" is not a viable option for us
We can't sell a Russian product to the US gov't.
We'll have to go back to building our own binary
Hey @nynymike! Quite embarrassing, appreciate you've reported it!
The certificates are actually renewed and provisioned automatically, so I've had it checked. The issue was surprisingly too long uptime of the http service, causing it to use old memory-cached cert for a month after its replacement on disk.
We've changed the provisioning to force config reloads.
The certificates are actually renewed and provisioned automatically, so I've had it checked. The issue was surprisingly too long uptime of the http service, causing it to use old memory-cached cert for a month after its replacement on disk.
We've changed the provisioning to force config reloads.
I'm looking for OpenDJ RestAPI document for community edition
same development path or not?
Hi @hasanakgoz, the two forks have the same origin, but different maintainers / developers. That's why the future development path is going to be generally different. Still, they can use our patches and we can use their patches, it's open source. :) Btw. former OpenDJ has been renamed to Wren:DS under Wren.