I tried via node to implement this.. It dint work out. I can check if new api on AuthenticationResource.java will help. As you have mentioned we will have to look at making this easy via configuration. Will take a look once i am done with this.
Regards, Sudha Jenslin > On 17-Oct-2017, at 8:11 AM, Jayesh Senjaliya <[email protected]> wrote: > > Hi Sudha, > > the web is implemented in NodeJS ( refer eagle-server/src/main/webapp ) > > do you have to have POST on home page? can it not be on any other endpoint? > in which case, it can also be implemented as another API enpoint in > (AuthenticationResource.java ) > so you should also check whether you can specify any other endpoint as a > proxy to the eagle app. > > may be we should add the support to easily add SSO support via > configuration later. > > Thanks > Jayesh > > > On Mon, Oct 16, 2017 at 6:19 PM, SUDHA JENSLIN <[email protected] > <mailto:[email protected]>> wrote: > >> I don’t think this is solving the issue. >> >> Can someone point me if there is documentation on how the fronted is >> implemented and how to work on the get post requests . This request is >> highly time critical. Can someone help on this? >> >> >> >> Regards, >> Sudha Jenslin >> >> >> >>> On 16-Oct-2017, at 3:45 PM, Firas Sghari <[email protected]> wrote: >>> >>> >>> Hello , >>> I recently joined the emailing listand I hope to be able to help :) >>> I think a reverse proxy can solve your cross domain problem. >>> Reverse proxy <https://en.wikipedia.org/wiki/Reverse_proxy >>> <https://en.wikipedia.org/wiki/Reverse_proxy>> >>> >>> Reverse proxy >>> Quite often, popular web servers use reverse-proxying functionality, >> shielding application frameworks of weaker ... >>> <https://en.wikipedia.org/wiki/Reverse_proxy >>> <https://en.wikipedia.org/wiki/Reverse_proxy>> >>> >>> >>> Regards , >>> SGHARI Firas >>> >>> >>> Le lundi 16 octobre 2017 à 12:05:11 UTC+2, SUDHA JENSLIN < >> [email protected] <mailto:[email protected]>> a écrit : >>> >>> >>> The purpose is to have the page rendered while a post call is made to >> the home page from the Single sigh on server. Ideally should have both get >> and post methods implemented for home page. >>> >>> Is there some way to enable post request on the home page so that it >> does not fail while a post request is sent from the server. Can you throw >> some light how how can we achieve it here.? Do you think any workaround can >> achieve this? >>> Note: I have done similar integrations earlier with couple of other >> applications where the authentication was successful and it returned back >> to the home page with post call. >>> >>> >>> I see the curl -X OPTIONS 'http://localhost:9090' <http://localhost:9090'> >>> < >> http://localhost:9090' <http://localhost:9090'>><http://localhost:9090' >> <http://localhost:9090'> <http://localhost:9090' <http://localhost:9090'>>> >> -i >>>> HTTP/1.1 200 OK >>>> Date: Fri, 13 Oct 2017 06:46:08 GMT >>>> Access-Control-Allow-Origin: * >>>> Access-Control-Allow-Methods: HEAD, POST, GET, PUT, OPTIONS, DELETE >>>> Access-Control-Max-Age: 3600 >>>> Access-Control-Allow-Headers: Origin, Accept, X-Requested-With, >> Content-Type, Access-Control-Request-Method, Access-Control-Request-Headers, >> Authorization >>>> Allow: GET, HEAD, TRACE, OPTIONS (here post is not allowed) >>>> Content-Length: 0 >>> >>> >>> We see the following for policies : enabled post as well since we create >> policies posting some details. >>> >>> curl -X OPTIONS http://localhost:9090/rest/metadata/policies/ >>> <http://localhost:9090/rest/metadata/policies/> < >> http://localhost:9090/rest/metadata/policies/ >> <http://localhost:9090/rest/metadata/policies/>>-i >>> HTTP/1.1 204 No Content >>> Date: Thu, 12 Oct 2017 20:49:28 GMT >>> Access-Control-Allow-Origin: * >>> Access-Control-Allow-Methods: HEAD, POST, GET, PUT, OPTIONS, DELETE >>> Access-Control-Max-Age: 3600 >>> Access-Control-Allow-Headers: Origin, Accept, X-Requested-With, >> Content-Type, Access-Control-Request-Method, Access-Control-Request-Headers, >> Authorization >>> Allow: OPTIONS,HEAD,DELETE,POST,GET >>> >>> >>> >>> Regards, >>> sudha Jenslin >>> >>> >>>> On 16-Oct-2017, at 3:19 PM, Chen, Hao <[email protected] >>>> <mailto:[email protected]> <mailto: >> [email protected] <mailto:[email protected]>>> wrote: >>>> >>>> What’s the purpose for this? >>>> >>>> The Access-Control-Allow-Methods: HEAD, POST, GET, PUT, OPTIONS, >> DELETE is just to resolve cross-domain problem[1], while in fact POST at >> root path “/” is not supported. >>>> >>>> [1] https://en.wikipedia.org/wiki/Cross-domain_solution >>>> <https://en.wikipedia.org/wiki/Cross-domain_solution> < >> https://en.wikipedia.org/wiki/Cross-domain_solution >> <https://en.wikipedia.org/wiki/Cross-domain_solution>><ht >> tps://en.wikipedia.org/wiki/Cross-domain_solution >> <tps://en.wikipedia.org/wiki/Cross-domain_solution> < >> https://en.wikipedia.org/wiki/Cross-domain_solution >> <https://en.wikipedia.org/wiki/Cross-domain_solution>>> >>>> >>>> Thanks, >>>> Hao >>>> >>>> From: SUDHA JENSLIN [mailto:[email protected] <mailto:[email protected]> >>>> <mailto: >> [email protected] <mailto:[email protected]>>] >>>> Sent: 2017年10月16日 14:47 >>>> To: [email protected] <mailto:[email protected]> >>>> <mailto:[email protected] <mailto:[email protected]>> >>>> Subject: Re: POST Method for home page >>>> >>>> >>>> >>>> >>>> I checked the methods allowed: >>>> >>>> curl -X OPTIONS 'http://localhost:9090' <http://localhost:9090'> >>>> <http://localhost:9090' <http://localhost:9090'>>< >> http://localhost:9090' <http://localhost:9090'> <http://localhost:9090' >> <http://localhost:9090'>>> -i >>>> HTTP/1.1 200 OK >>>> Date: Fri, 13 Oct 2017 06:46:08 GMT >>>> Access-Control-Allow-Origin: * >>>> Access-Control-Allow-Methods: HEAD, POST, GET, PUT, OPTIONS, DELETE >>>> Access-Control-Max-Age: 3600 >>>> Access-Control-Allow-Headers: Origin, Accept, X-Requested-With, >> Content-Type, Access-Control-Request-Method, Access-Control-Request-Headers, >> Authorization >>>> Allow: GET, HEAD, TRACE, OPTIONS >>>> Content-Length: 0 >>>> >>>> >>>> -Sudha Jenslin >>>> >>>> >>>> >>>> On 16-Oct-2017, at 12:14 PM, SUDHA JENSLIN <[email protected] >>>> <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>> >> <mailto:[email protected] <mailto:[email protected]> <mailto: >> [email protected] <mailto:[email protected]>>>> wrote: >>>> >>>> >>>> I am trying integrate apache eagle single sign on. While doing so the >> return call(http://machinename:9090/ <http://machinename:9090/> >> <http://machinename:9090/ <http://machinename:9090/>><htt >> p://machinename:9090/ <p://machinename:9090/> <http://machinename:9090/ >> <http://machinename:9090/>>>) is sent back as post >> call after authentication is done. >>>> >>>> But the request fails with 405 error. When i checked for the allowed >> methods on the url: >>>> i saw : >>>> Allow: GET, HEAD, TRACE, OPTIONS. >>>> >>>> >>>> How to enable it with post method as well for the url.? >>>> >>>> >>>> Error message for your reference: >>>> <PastedGraphic-1.tiff> >>>> >>>> Thanks, >>>> Sudha Jenslin >>>> >>>> >>>> >>>> On 15-Oct-2017, at 8:09 PM, Chen, Hao <[email protected] >>>> <mailto:[email protected]> <mailto: >> [email protected] <mailto:[email protected]>> <mailto:[email protected] >> <mailto:[email protected]> <mailto:[email protected] >> <mailto:[email protected]>>>> >> wrote: >>>> >>>> Hi Sudha, >>>> >>>> >>>> What's the technical requirement? I think here POST is already >> supported. >>>> >>>> >>>> Thanks, >>>> >>>> Hao >>>> >>>> ________________________________ >>>> From: SUDHA JENSLIN <[email protected] <mailto:[email protected]> >>>> <mailto:[email protected] <mailto:[email protected]>> >> <mailto:[email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>>>> >>>> Sent: Sunday, October 15, 2017 1:22 PM >>>> To: [email protected] <mailto:[email protected]> >>>> <mailto:[email protected] <mailto:[email protected]>> <mailto: >> [email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>>> >>>> Subject: Re: POST Method for home page >>>> >>>> Can some suggest on the below request... >>>> >>>> >>>> Thanks, >>>> Sudha jenslin >>>> >>>> On Friday, October 13, 2017, SUDHA JENSLIN <[email protected] >>>> <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>> >> <mailto:[email protected] <mailto:[email protected]> <mailto: >> [email protected] <mailto:[email protected]>>>> wrote: >>> >>>> >>>> >>>> Hi Team, >>>> >>>> There is a requirement that needs to have the POST method enabled on >> the >>>> home page(http://localhost:9090/ <http://localhost:9090/> >>>> <http://localhost:9090/ <http://localhost:9090/>><http: >> //localhost:9090/ <http://localhost:9090/ <http://localhost:9090/>>>). How >> can i get it done. >>>> >>>> Currently i see the following methods being allowed. >>>> >>>> HTTP/1.1 200 OK >>>> Date: Thu, 12 Oct 2017 20:50:37 GMT >>>> Access-Control-Allow-Origin: * >>>> Access-Control-Allow-Methods: HEAD, POST, GET, PUT, OPTIONS, DELETE >>>> Access-Control-Max-Age: 3600 >>>> Access-Control-Allow-Headers: Origin, Accept, X-Requested-With, >>>> Content-Type, Access-Control-Request-Method, Access-Control-Request- >> Headers, >>>> Authorization >>>> *Allow: GET, HEAD, TRACE, OPTIONS* >>>> Content-Length: 0 >>>> >>>> >>>> Can someone Provide me input here on enabling POST as well for this. >>>> >>>> Thanks, >>>> Sudha jenslin
