RE: [users@httpd] JWT could not be decrypted

2019-01-08 Thread MARASOIU Nicolae-dumitru (renexter)
Hi Jonathon and all, The error is received upon parsing the response from the IdP token endpoint, so I believe that using the single RS256 public key provided by jwks could not be properly used to decrypt the jwt id token or jwt access token, but I will try to verify this hypothesis, Thank you,

Re: [users@httpd] URGENT: Apache HTTP Migration from 1.3 to 2.4 UNIX Solaris

2019-01-08 Thread singhal . ankit
Hi Dennis, I can get the httpd service running if I do not load my module(example_module) If I comment this module then apache starts running. So the problem is with my module only. Maybe I am missing something from the configuration point. Here "s = 0x1 """ and it is passing as

Re: [users@httpd] URGENT: Apache HTTP Migration from 1.3 to 2.4 UNIX Solaris

2019-01-08 Thread Dennis Clarke
Could you please suggest whether need to make more entries in the httpd.conf of command entries? Can you get the httpd service running without any modifications and without excessive modules ? Dennis - To unsubscribe,

Re: [users@httpd] JWT could not be decrypted

2019-01-08 Thread Jonathon Koyle
Doesn't get use the authorization header? Is it possible that you are overriding the provided jwt token when you set the header for your basic auth? On Tue, Jan 8, 2019, 09:06 MARASOIU Nicolae-dumitru (renexter) < nicolae-dumitru.marasoiu-ext...@renault.com wrote: > Hi all, > > We receive this

Re: [users@httpd] URGENT: Apache HTTP Migration from 1.3 to 2.4 UNIX Solaris

2019-01-08 Thread singhal . ankit
Hi William, Thank you for the response. I have compiled the code with -g option. Please find the excerpts from the code and httpd.conf file: Code declaration: static const command_rec example_cmds[] = { ("SCENARIO",CallScenarioName,NULL,RSRC_CONF,"Define scenario name"), {NULL} };

Re: [users@httpd] URGENT: Apache HTTP Migration from 1.3 to 2.4 UNIX Solaris

2019-01-08 Thread Dennis Clarke
On 1/8/19 1:29 PM, singhal.an...@tcs.com wrote: Hi Dennis, Thank you for the response..!! Right, that is an old Sun sparc "coolthreads" server of some sort. Looks like Solaris 11. I do not exactly understand by toolchain? Could you please elaborate more of what information I can provide?

Re: [users@httpd] URGENT: Apache HTTP Migration from 1.3 to 2.4 UNIX Solaris

2019-01-08 Thread singhal . ankit
Hi Dennis, Thank you for the response..!! Following are the specifications: I do not exactly understand by toolchain? Could you please elaborate more of what information I can provide? On the same environment, we were running apache 1.3 successfully. In this we are using a user

Re: [users@httpd] URGENT: Apache HTTP Migration from 1.3 to 2.4 UNIX Solaris

2019-01-08 Thread William A Rowe Jr
On Tue, Jan 8, 2019 at 10:48 AM wrote: > > I have migrated a user module mod_example from 1.3 to 2.4. But when I try > to start the apache it is giving a segmentation fault and creating a core. > > Following is the stacktrace while debug: > t@1 (l@1) signal SEGV (no mapping at the fault address)

Re: [users@httpd] URGENT: Apache HTTP Migration from 1.3 to 2.4 UNIX Solaris

2019-01-08 Thread Dennis Clarke
On 1/8/19 11:48 AM, singhal.an...@tcs.com wrote: Dear All, I have migrated a user module mod_example from 1.3 to 2.4. But when I try to start the apache it is giving a segmentation fault and creating a core. Installed binaries: Apache 2.4.34 apr-1.6.5 apr-util-1.6.1 pcre-8.40 expat-2.1.0

[users@httpd] URGENT: Apache HTTP Migration from 1.3 to 2.4 UNIX Solaris

2019-01-08 Thread singhal . ankit
Dear All, I have migrated a user module mod_example from 1.3 to 2.4. But when I try to start the apache it is giving a segmentation fault and creating a core. Installed binaries: Apache 2.4.34 apr-1.6.5 apr-util-1.6.1 pcre-8.40 expat-2.1.0 Following is the stacktrace while debug: t@1 (l@1)

[users@httpd] JWT could not be decrypted

2019-01-08 Thread MARASOIU Nicolae-dumitru (renexter)
Hi all, We receive this error in the log file, "JWT could not be decrypted", and I give details below, we would need a bit of help to figure out the cause of the error. In my understanding the IdP exposes an http endpoint called jwks where the set of keys and associated encryption types