Authentication issue after build client war file

[David Rodriguez <dj...@gmail.com>]

Hi,
I have build from git both the server and client versions, to be able to
use the Spanish keyboard layout in the Guacamole connections.

Server version was build and installed without issues and can continue
using the previous .war client file to connect, however copying the new
.war file and after restarting Tomcat, I'm unable to login as it seems that
my credentials are not recognized.
Is there any missed step I should do additionally to build and replace the
.war file? Just FYI if I copy back the previous version of .war file, login
works properly

Thanks

Re: Authentication issue after build client war file

[David Rodriguez <dj...@gmail.com>]

Fixed also the translation :)

2017-12-05 10:55 GMT+01:00 David Rodriguez <dj...@gmail.com>:

> Thanks a lot Mike
>
> With the mvn clean install the Sp keyb layout appears although it doesn't
> take the translation string ""FIELD_OPTION_SERVER_LAYOUT_ES_ES_QWERTY" :
> "Spanish (Qwerty)"," but works what is the important thing for me :)
>
> Anyway I will keep looking to the site to see if a new version is
> published, so will update from there instead my build to avoid this kind of
> things.
>
>
> Thanks again!!
>
> 2017-12-05 8:17 GMT+01:00 Mike Jumper <mi...@guac-dev.org>:
>
>> On Mon, Dec 4, 2017 at 7:48 AM, David Rodriguez <dj...@gmail.com> wrote:
>>
>>> Hi there,
>>>
>>> Any clue why I still unable to see the Spanish keyboard layout after
>>> follow the steps mentioned before?
>>>
>>>
>> The contents of the keyboard layout field within the connection
>> parameters in the admin UI are determined by the "rdp.json" file which you
>> edited. Assuming that the edit was correct (you didn't accidentally produce
>> invalid JSON), that should be all you need for the choice to be made
>> available. You don't even technically need to add the translation - it will
>> appear as a huge uppercase machine-readable string, but will still be a
>> choice.
>>
>> If the choice is not available at all, then the only possibility is that
>> the version of Guacamole deployed was not built against the guacamole-ext
>> that you modified. This could be because:
>>
>> 1) Tomcat did not actually redeploy Guacamole when you copied the new
>> guacamole.war over (you may need to clear the working directory containing
>> the exploded contents of the .war and restart Tomcat to force Tomcat to
>> re-extract and redeploy)
>> 2) You did not copy the new guacamole.war over
>> 3) The "guacamole" project within guacamole-client was not rebuilt
>> against the "guacamole-ext" containing your modifications
>>
>> If nothing is working in your attempts to resolve this, I would suggest:
>>
>> 1) Doing a full "mvn clean install" from the root of the
>> "guacamole-client" source directory. This will rebuild absolutely
>> everything, and will ensure guacamole is built against your modified
>> guacamole-ext.
>> 2) Stop Tomcat
>> 3) Remove the existing guacamole.war and associated guacamole/ directory
>> (automatically created by Tomcat upon deployment)
>> 4) Copy guacamole/target/guacamole*.war in place
>> 5) Start Tomcat
>> 6) Verify that Tomcat automatically extracted the .war
>>
>> At that point, assuming your changes are indeed present on the source
>> tree you built, the choice should now be available.
>>
>> Looking back at GUACAMOLE-233, though ... this shouldn't be necessary.
>> The keymap was added at the guacamole-server level, and should also have
>> been added to guacamole-client. I've reopened the issue in JIRA, as this
>> was definitely an oversight.
>>
>> - Mike
>>
>>
>

Re: Authentication issue after build client war file

[David Rodriguez <dj...@gmail.com>]

Thanks a lot Mike

With the mvn clean install the Sp keyb layout appears although it doesn't
take the translation string ""FIELD_OPTION_SERVER_LAYOUT_ES_ES_QWERTY" :
"Spanish (Qwerty)"," but works what is the important thing for me :)

Anyway I will keep looking to the site to see if a new version is
published, so will update from there instead my build to avoid this kind of
things.


Thanks again!!

2017-12-05 8:17 GMT+01:00 Mike Jumper <mi...@guac-dev.org>:

> On Mon, Dec 4, 2017 at 7:48 AM, David Rodriguez <dj...@gmail.com> wrote:
>
>> Hi there,
>>
>> Any clue why I still unable to see the Spanish keyboard layout after
>> follow the steps mentioned before?
>>
>>
> The contents of the keyboard layout field within the connection parameters
> in the admin UI are determined by the "rdp.json" file which you edited.
> Assuming that the edit was correct (you didn't accidentally produce invalid
> JSON), that should be all you need for the choice to be made available. You
> don't even technically need to add the translation - it will appear as a
> huge uppercase machine-readable string, but will still be a choice.
>
> If the choice is not available at all, then the only possibility is that
> the version of Guacamole deployed was not built against the guacamole-ext
> that you modified. This could be because:
>
> 1) Tomcat did not actually redeploy Guacamole when you copied the new
> guacamole.war over (you may need to clear the working directory containing
> the exploded contents of the .war and restart Tomcat to force Tomcat to
> re-extract and redeploy)
> 2) You did not copy the new guacamole.war over
> 3) The "guacamole" project within guacamole-client was not rebuilt against
> the "guacamole-ext" containing your modifications
>
> If nothing is working in your attempts to resolve this, I would suggest:
>
> 1) Doing a full "mvn clean install" from the root of the
> "guacamole-client" source directory. This will rebuild absolutely
> everything, and will ensure guacamole is built against your modified
> guacamole-ext.
> 2) Stop Tomcat
> 3) Remove the existing guacamole.war and associated guacamole/ directory
> (automatically created by Tomcat upon deployment)
> 4) Copy guacamole/target/guacamole*.war in place
> 5) Start Tomcat
> 6) Verify that Tomcat automatically extracted the .war
>
> At that point, assuming your changes are indeed present on the source tree
> you built, the choice should now be available.
>
> Looking back at GUACAMOLE-233, though ... this shouldn't be necessary. The
> keymap was added at the guacamole-server level, and should also have been
> added to guacamole-client. I've reopened the issue in JIRA, as this was
> definitely an oversight.
>
> - Mike
>
>

Re: Authentication issue after build client war file

[Mike Jumper <mi...@guac-dev.org>]

On Mon, Dec 4, 2017 at 7:48 AM, David Rodriguez <dj...@gmail.com> wrote:

> Hi there,
>
> Any clue why I still unable to see the Spanish keyboard layout after
> follow the steps mentioned before?
>
>
The contents of the keyboard layout field within the connection parameters
in the admin UI are determined by the "rdp.json" file which you edited.
Assuming that the edit was correct (you didn't accidentally produce invalid
JSON), that should be all you need for the choice to be made available. You
don't even technically need to add the translation - it will appear as a
huge uppercase machine-readable string, but will still be a choice.

If the choice is not available at all, then the only possibility is that
the version of Guacamole deployed was not built against the guacamole-ext
that you modified. This could be because:

1) Tomcat did not actually redeploy Guacamole when you copied the new
guacamole.war over (you may need to clear the working directory containing
the exploded contents of the .war and restart Tomcat to force Tomcat to
re-extract and redeploy)
2) You did not copy the new guacamole.war over
3) The "guacamole" project within guacamole-client was not rebuilt against
the "guacamole-ext" containing your modifications

If nothing is working in your attempts to resolve this, I would suggest:

1) Doing a full "mvn clean install" from the root of the "guacamole-client"
source directory. This will rebuild absolutely everything, and will ensure
guacamole is built against your modified guacamole-ext.
2) Stop Tomcat
3) Remove the existing guacamole.war and associated guacamole/ directory
(automatically created by Tomcat upon deployment)
4) Copy guacamole/target/guacamole*.war in place
5) Start Tomcat
6) Verify that Tomcat automatically extracted the .war

At that point, assuming your changes are indeed present on the source tree
you built, the choice should now be available.

Looking back at GUACAMOLE-233, though ... this shouldn't be necessary. The
keymap was added at the guacamole-server level, and should also have been
added to guacamole-client. I've reopened the issue in JIRA, as this was
definitely an oversight.

- Mike

Re: Authentication issue after build client war file

[David Rodriguez <dj...@gmail.com>]

Hi there,

Any clue why I still unable to see the Spanish keyboard layout after follow
the steps mentioned before?

Thanks

2017-12-02 8:21 GMT+01:00 David Rodriguez <dj...@gmail.com>:

> Hi Nick
>
> What Im unable to see is the Spanish keyboard layout option inside the
> connection settings.
>
> El 2 dic. 2017 3:25, "Nick Couchman" <ni...@gmail.com> escribió:
>
>>
>> On Fri, Dec 1, 2017 at 18:18 David Rodriguez <dj...@gmail.com> wrote:
>>
>>> Thanks MIke
>>>
>>> It was due to the mysql schema upgrade. I'm able now to login correctly,
>>> however the layout still not appearing.
>>>
>>
>> Could you clarify what you mean when you say the layout is not
>> appearing?  Is this right after you login, or at some other point.  Maybe
>> describe the steps you're going through and what you're seeing vs. what
>> your expect to see?
>>
>> -Nick
>>
>>>

Re: Authentication issue after build client war file

[David Rodriguez <dj...@gmail.com>]

Hi Nick

What Im unable to see is the Spanish keyboard layout option inside the
connection settings.

El 2 dic. 2017 3:25, "Nick Couchman" <ni...@gmail.com> escribió:

>
> On Fri, Dec 1, 2017 at 18:18 David Rodriguez <dj...@gmail.com> wrote:
>
>> Thanks MIke
>>
>> It was due to the mysql schema upgrade. I'm able now to login correctly,
>> however the layout still not appearing.
>>
>
> Could you clarify what you mean when you say the layout is not appearing?
> Is this right after you login, or at some other point.  Maybe describe the
> steps you're going through and what you're seeing vs. what your expect to
> see?
>
> -Nick
>
>>

Re: Authentication issue after build client war file

[Nick Couchman <ni...@gmail.com>]

On Fri, Dec 1, 2017 at 18:18 David Rodriguez <dj...@gmail.com> wrote:

> Thanks MIke
>
> It was due to the mysql schema upgrade. I'm able now to login correctly,
> however the layout still not appearing.
>

Could you clarify what you mean when you say the layout is not appearing?
Is this right after you login, or at some other point.  Maybe describe the
steps you're going through and what you're seeing vs. what your expect to
see?

-Nick

>

Re: Authentication issue after build client war file

[David Rodriguez <dj...@gmail.com>]

Thanks MIke

It was due to the mysql schema upgrade. I'm able now to login correctly,
however the layout still not appearing. I have follow the steps you
mentioned on https://issues.apache.org/jira/browse/GUACAMOLE-233, so I did
the following:
- git cloned both server and client
- on server folder: checked src/protocols/rdp/Makefile.am on server files
to see if "keymaps/es_es_qwertz.keymap" was in the rdp_keymaps section. (It
was already there). Compiled and Installed server successfully
-on client folder: added "es-es-qwerty", to
guacamole-ext/src/main/resources/org/apache/guacamole/protocols/rdp.json on
server layout section.
-on client folder: added ""FIELD_OPTION_SERVER_LAYOUT_ES_ES_QWERTY" :
"Spanish (Qwerty)"," to guacamole/src/main/webapp/translations/en.json
-client .war generated successfully
-upgraded mysql schema

any suggestion?

Thanks




2017-12-01 21:03 GMT+01:00 Mike Jumper <mi...@guac-dev.org>:

> On Fri, Dec 1, 2017 at 10:47 AM, David Rodriguez <dj...@gmail.com> wrote:
>
>> Hi,
>> I have build from git both the server and client versions, to be able to
>> use the Spanish keyboard layout in the Guacamole connections.
>>
>> Server version was build and installed without issues and can continue
>> using the previous .war client file to connect, however copying the new
>> .war file and after restarting Tomcat, I'm unable to login as it seems that
>> my credentials are not recognized.
>> Is there any missed step I should do additionally to build and replace
>> the .war file? Just FYI if I copy back the previous version of .war file,
>> login works properly
>>
>>
> Please check your Tomcat logs. The web application will refuse to load
> extensions from older versions, as those extensions (and their
> configurations) will not be compatible. If this is the case, there should
> be an error or warning in the logs regarding the incompatible extension.
>
> In addition to updating guacamole-server and the guacamole .war, you will
> need to install the updated versions of any installed Guacamole extensions,
> and double-check your configuration against the current install
> instructions to make sure nothing else needs to be updated. If using a
> database for authentication, for example, you will likely need to run one
> or more SQL scripts to upgrade the schema.
>
> - Mike
>
>

Re: Authentication issue after build client war file

[Mike Jumper <mi...@guac-dev.org>]

On Fri, Dec 1, 2017 at 10:47 AM, David Rodriguez <dj...@gmail.com> wrote:

> Hi,
> I have build from git both the server and client versions, to be able to
> use the Spanish keyboard layout in the Guacamole connections.
>
> Server version was build and installed without issues and can continue
> using the previous .war client file to connect, however copying the new
> .war file and after restarting Tomcat, I'm unable to login as it seems that
> my credentials are not recognized.
> Is there any missed step I should do additionally to build and replace the
> .war file? Just FYI if I copy back the previous version of .war file, login
> works properly
>
>
Please check your Tomcat logs. The web application will refuse to load
extensions from older versions, as those extensions (and their
configurations) will not be compatible. If this is the case, there should
be an error or warning in the logs regarding the incompatible extension.

In addition to updating guacamole-server and the guacamole .war, you will
need to install the updated versions of any installed Guacamole extensions,
and double-check your configuration against the current install
instructions to make sure nothing else needs to be updated. If using a
database for authentication, for example, you will likely need to run one
or more SQL scripts to upgrade the schema.

- Mike