Perl 6 - the future is here, just unevenly distributed

IRC log for #openam, 2017-04-07

| Channels | #openam index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:48 ilbot3 joined #openam
01:48 Topic for #openam is now Chat about the OpenAM project - https://backstage.forgerock.com/#/downloads - OpenAM 13.5.0 is out! OpenAM 12.0.4 is out! Channel logs at: http://irclog.perlgeek.de/openam/today
05:11 aldaris joined #openam
07:16 aldaris joined #openam
08:27 FireBurn|Work Morning, I switched from using a preserved maven respository to build OpenAM to MegaMatt's script
08:27 aldaris is it working for you?
08:28 FireBurn|Work However when I try and create a new install I get the following error " 'Cannot read the bind response from the server. The port youare using may require a secured communication (--useSSL).SocketTimeoutException(Read timed out)'"
08:28 aldaris which command fails?
08:28 FireBurn|Work Installing OpenAM configuration store in /apps/was/openam/opends...Success.
08:28 FireBurn|Work Creating OpenAM suffixYou have provided options for scheduling this operation as a task but optionsprovided for connecting to the server's tasks backend resulted in thefollowing error: 'Cannot read the bind response from the server. The port youare using may require a secured communication (--useSSL).SocketTimeoutException(Read timed out)'
08:29 FireBurn|Work Error loading OpenAM suffix 1
08:29 aldaris ah, so you were able to compile it, but fail to install it?
08:29 FireBurn|Work emb.creatingfamsuffix.failure, refer to install.log under /apps/was/openam for more information
08:29 aldaris that sounds like a network related issue, are you sure that the hostname you've used is accessible and maps to a local network interface?
08:33 FireBurn|Work No network issues, and this worked the other day with a compiled version from the old POMs I still had lying about
08:33 FireBurn|Work https://pastebin.com/uDC1A8uh
08:33 FireBurn|Work I've removed my company name from log
08:34 aldaris what do you get if you try to connect to ut005950:4444 ?
08:34 aldaris ut005950 does not sound like a proper hostname for DJ, it really should be a fully qualified domain name AFAIK
08:38 FireBurn|Work Connect with what?
08:42 FireBurn|Work openssl s_client -connect ut005950:4444       CONNECTED(00000003)
08:42 aldaris what is the CN in the certificate?
08:43 FireBurn|Work When I connect to ut005950:10110 I get the nodeagent cert ut005950
08:44 FireBurn|Work That's why I'm not using the fully qualified domain name
08:45 aldaris you should be able to control the hostname for embedded DJ only
08:45 aldaris I think the configurator CLI app allows you to do that
08:46 FireBurn|Work DIRECTORY_SERVER=localhost
08:46 FireBurn|Work Like I said when I was using the old poms this all worked fine
08:46 FireBurn|Work It was when I switched to using the self compiled version that I started having issues
08:46 aldaris POMs shouldn't make a difference theoretically
08:47 aldaris I would suggest to debug it, I don't really have a better advice
08:50 FireBurn|Work The only thing I can think of is the version downloaded from forgerock maven had patches installed
08:51 FireBurn|Work Or were compiled with a different version of java
08:53 aldaris unlikely
08:53 aldaris the release builds are always created from the tag
08:54 aldaris java version during compilation very rarely makes a difference in final binaries
09:09 FireBurn|Work Weird, it works fine with tomcat (granted using fully qualified name)
09:10 FireBurn|Work Let me try a few more things
09:13 FireBurn|Work I'm wondering if it has something to do with using WebSphere, but I'm not sure why it would work previously and stop working now
09:20 FireBurn|Work Using fully qualified name (but insecure port) I'm getting the same error
09:20 FireBurn|Work Will switch back to the old build method
10:07 FireBurn|Work joined #openam
10:07 FireBurn|Work Hi again
10:07 FireBurn|Work I can confirm that building using my saved maven repo allows things to build and install again
10:11 aldaris joined #openam
10:12 FireBurn|Work aldaris: Not sure if you saw that or not, switching back to the old build process (saved maven repo) allows OpenAM to build and more improtantly install
10:13 aldaris magic, would love to know why
10:20 FireBurn|Work Me too, would prefer having a repeatable build
10:39 FireBurn|Work Is there a guide or doc somewhere that lists all the REST calls that can be used with curl?
10:43 aldaris there is API descriptor in Access Manager 5
10:47 FireBurn|Work Where about?
10:48 FireBurn|Work AM5 was a disaster with WebSphere btw
10:52 FireBurn|Work joined #openam
10:52 FireBurn|Work joined #openam
10:58 MegaMatt joined #openam
11:01 HelgeO joined #openam
11:18 aldaris joined #openam
12:08 aldaris joined #openam
12:53 aldaris joined #openam
13:01 FireBurn|Work This fixes all the issues I was having with ssoadm: https://bugster.forgerock.org/jira/si/jira.issueviews:issue-html/OPENAM-8042/OPENAM-8042.html
13:53 FireBurn|Work Hi MegaMatt
13:54 MegaMatt Hi
13:54 FireBurn|Work I tried using your script to build OpenAM cleanly. it built but installation failed with OpenDJ issues
13:54 MegaMatt Mine? I don’t have such a script
13:55 aldaris it was my script, but I don't want to take credit any more :)
13:55 FireBurn|Work lol
13:55 FireBurn|Work Well it builds
13:55 FireBurn|Work So in a sense its a success
13:55 FireBurn|Work though I did have to change the ordering slighlty when I used jenkins
13:56 FireBurn|Work https://gist.github.com/FireBurn/b1d677ded6bcd9831679ef1ebb50efab
14:46 FireBurn|Work I've uploaded the dodgy war here: https://www.dropbox.com/s/y49tyzvsb33jcr4/OpenAM-13.0.0.war?dl=0
16:33 FireBurn joined #openam
17:08 aldaris joined #openam
18:05 aldaris joined #openam
19:34 aldaris joined #openam

| Channels | #openam index | Today | | Search | Google Search | Plain-Text | summary