Hello,
To clarify, are you trying to get to a point where the password to the Oracle
schema looks something like this in server.xml?
password="2d9377fee736w1115ca984a1dfb99c943"
instead of unencrypted like
password=
so that someone wandering around your server can't get the password to your
O
On 24/10/2018 19:01, Robert J. Carr wrote:
Hi Mark-
Thanks again for the response.
I fixed the credential handler config, it just had a superfluous attribute,
so the WARNING went away and as you predicted didn't change the session
outcome. Now when stopping and starting tomcat I'm not seeing a
Hi Mark-
Thanks again for the response.
I fixed the credential handler config, it just had a superfluous attribute,
so the WARNING went away and as you predicted didn't change the session
outcome. Now when stopping and starting tomcat I'm not seeing any log
higher than an INFO, it is appears to
On October 24, 2018 3:50:59 PM UTC, "Robert J. Carr" wrote:
>> > * if the server is shut down and restarted then everything seems to
>> >disappear, as I then get a 403 when trying to access the protected
>page
>>
>> Expected behaviour here will depend on whether a server shutdown
>shuts
>down Tom
Hi Mark-
Thanks for the response.
> > * if the application is undeployed and redeployed (while the server
> >remains running) a new session is silently generated, and any contents
> >disappear, but the user maintains her authentication
>
> As expected. Redeploy (undeploy+deploy) != reload (stop+
