Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D64B7200C02 for ; Fri, 20 Jan 2017 19:52:28 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id D4C46160B48; Fri, 20 Jan 2017 18:52:28 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D30E1160B34 for ; Fri, 20 Jan 2017 19:52:27 +0100 (CET) Received: (qmail 85055 invoked by uid 500); 20 Jan 2017 18:52:22 -0000 Mailing-List: contact user-help@guacamole.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@guacamole.incubator.apache.org Delivered-To: mailing list user@guacamole.incubator.apache.org Received: (qmail 85043 invoked by uid 99); 20 Jan 2017 18:52:22 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2017 18:52:22 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 8B9E2181B9D for ; Fri, 20 Jan 2017 18:52:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.379 X-Spam-Level: ** X-Spam-Status: No, score=2.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=webaula.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id eWZMGgcJdSSM for ; Fri, 20 Jan 2017 18:52:19 +0000 (UTC) Received: from mail-yw0-f177.google.com (mail-yw0-f177.google.com [209.85.161.177]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 4228A5F54F for ; Fri, 20 Jan 2017 18:52:19 +0000 (UTC) Received: by mail-yw0-f177.google.com with SMTP id u68so59398774ywg.0 for ; Fri, 20 Jan 2017 10:52:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=webaula.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Q1hYLTzHoaZRuYkDdtYiP1OzCDC55FnQM3ifJReQVZM=; b=J9dhkWtqpt12zC3Em4uHZEYFFi10pL+kxq8ZVBo6dYRoKpUR2iFx6I+ISTVFMxe3KM KB4PSgOBGcTNlfFCq1lTgv/TM3O7MxXPHD2sLeYd2N6jN37pfoOcRJfNtWCslRTfzqen 6AzN2I9uqzlI9HHmyZVBxCqk4JEttaCg0QpDI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Q1hYLTzHoaZRuYkDdtYiP1OzCDC55FnQM3ifJReQVZM=; b=joeWv2oI/+frfo+LrDKomJ/XIFY0RPpqIqJ1vuCyCIKtG3G5DheLPvvM/owl8fZvbs VSgDA9W0ywjuMNAQBL6bqL2zJHtLc41acxiDv5AeL6NiqZodoDfpYgDLSWWccdKtacX5 25OAhqqLEIrGaz7Cs1qe4dFDPd0ngO0cnj/mNmN7HHqYgYXehL3AhCsZbCj/pbAv7CTV zcsQ5FDaaI2BPfeQQ/37xtWCN33dhxlqjmLdxwq49gbg65G94pOAba3Bi9j2XlrbPae+ Qttsazm/Rj+2+ZX3DGDZm0WlxAvJLxoVrBULKfw2DLd/s/YNd43w6lQCR4AJ3MMP3ZKa Lgtw== X-Gm-Message-State: AIkVDXIOQlh0LjvUMUJWlCyAgXugjca8D82UrW7S6gzHj2cIRGtMa5yAzoRGX4kXBqvQ8h6l8Lptm67vge1WYQ== X-Received: by 10.55.209.203 with SMTP id o72mr13576603qkl.281.1484938337777; Fri, 20 Jan 2017 10:52:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.28.73 with HTTP; Fri, 20 Jan 2017 10:51:37 -0800 (PST) In-Reply-To: References: From: Jorge Camara Date: Fri, 20 Jan 2017 16:51:37 -0200 Message-ID: Subject: Re: Branding the login page To: user@guacamole.incubator.apache.org Content-Type: multipart/alternative; boundary=001a1149b0a423102f05468b2626 archived-at: Fri, 20 Jan 2017 18:52:29 -0000 --001a1149b0a423102f05468b2626 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Nice. Thank you!!! *Atenciosamente,* *Jorge Camara* Analista de Suporte S=C3=AAnior - *Centro de Tecnologia* *www.webaula.com.br* +55 (31) 2129-0550 2017-01-20 16:44 GMT-02:00 Mike Jumper : > On Fri, Jan 20, 2017 at 10:18 AM, Jorge Camara > wrote: > >> Hi, >> >> The name "Apache Guacamole" you can change on translations files : >> >> ...tomcat8/webappas/guacamole/translations/en.json >> >> and the logo you can change in directory: >> >> ...tomcat8/webapps/guacamole/images/ >> >> > It's not recommended to modify these files within Tomcat's webapps > directory, as it will not be stable across redeploys or upgrades. Part of > the point of providing this functionality through extensions is to keep > these kinds of customizations independent from Tomcat, the webapp, upstre= am > changes, etc. > > To achieve the same with an extension, you would create a .zip file named > "whatever-you-want-to-call-it.jar" containing: > > * A "guac-manifest.json" file describing the contents of the extension > (more on this below). The format of this is described here: > http://guacamole.incubator.apache.org/doc/gug/guacamole-ext.html#ext- > manifest > * An image to be used as the logo (declared within the "resources" sectio= n > of guac-manifest.json) > * A translation file overriding the strings you wish to override (declare= d > within the "translations" section of guac-manifest.json) > * A CSS file which overrides the style of the login screen, applying your > logo (declared within the "css" section of guac-manifest.json) > > Your guac-manifest.json would end up looking like: > > { > "guacamoleVersion" : "*", > "name" : "Some meaningful, human-readable name", > "namespace" : "some-unique-namespace", > > "css" : [ > "css/login-override.css" > ], > > "resources" : [ > "resources/your-logo.png" : "image/png" > ], > > "translations" : [ > "translations/en.json" > ] > > } > > css/login-override.css: > > .login-ui .login-dialog .logo { > background-image: url('app/ext/some-unique- > namespace/resources/your-logo.png'); > } > > translations/en.json: > > { > "APP" : { > "NAME" : "Name of Your Choice", > } > } > > And then "resources/your-logo.png" as well. > > Once all that is zipped together and dropped into > GUACAMOLE_HOME/extensions/ as a .jar file, it will automatically be loade= d > by Guacamole when the webapp starts. The custom CSS will be appended to t= he > existing CSS, overriding the original styles, the custom translations wil= l > be overlaid on the existing translations, overriding only the strings you > specify, and the custom logo will be served dynamically from within a > directory named after your chosen namespace. You'll probably want to make > other changes to the CSS, especially if your logo has a different aspect > ratio, but this is a start. > > Other than overriding the CSS, there's really not much programming > involved; it's a matter of adding whatever files you need to override wha= t > you're looking to override, and then declaring those files within > "guac-manifest.json": > > http://guacamole.incubator.apache.org/doc/gug/guacamole- > ext.html#ext-manifest > > - Mike > > --001a1149b0a423102f05468b2626 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Nice. Thank you!!!

Atenciosamente,

Jorge Camara

Analista de Suporte S= =C3=AAnior -=C2=A0Centro de Tecnologia

www= .webaula.com.br
+55 (31) 2129-0550


=

2017-01-20 16:44 GMT-02:00 Mike Jumper <mike.jumper@guac-dev.org>:
= On Fri, Jan 20, 2017 at 10:18 AM, Jorge Camara <jorge.camara@webaul= a.com> wrote:
Hi,

The name "Apache Guacamo= le" you can change on translations files :

..= .tomcat8/webappas/guacamole/translations/en.json

<= div>and the logo you can change in directory:

...tomcat8/webapps/gua= camole/images/


It's not recommended to modify = these files within Tomcat's webapps directory, as it will not be stable= across redeploys or upgrades. Part of the point of providing this function= ality through extensions is to keep these kinds of customizations independe= nt from Tomcat, the webapp, upstream changes, etc.

To achieve the same with an extension, you would create a .zip file named = "whatever-you-want-to-call-it.jar" containing:
* A "guac-manifest.json" file describing the contents= of the extension (more on this below). The format of this is described her= e:=C2=A0http://guacamole.incubator.ap= ache.org/doc/gug/guacamole-ext.html#ext-manifest
* = An image to be used as the logo (declared within the "resources" = section of guac-manifest.json)
* A translation file overriding th= e strings you wish to override (declared within the "translations"= ; section of guac-manifest.json)
* A CSS file which overrides the= style of the login screen, applying your logo (declared within the "c= ss" section of guac-manifest.json)

Your guac-= manifest.json would end up looking like:

=C2=A0 = =C2=A0 {
=C2=A0 =C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0"guacamoleVer= sion" : "*",
=C2=A0 =C2=A0 =C2=A0 =C2=A0 "nam= e" : "Some meaningful, human-readable name",
= =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0"namespace" : "some-unique-= namespace",

=C2=A0 =C2=A0 =C2=A0 =C2=A0 "= ;css" : [
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0&qu= ot;css/login-override.css"
=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0= ],

=C2=A0 =C2=A0 =C2=A0 =C2=A0 "resources&quo= t; : [
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0"resou= rces/your-logo.png" : "image/png"
=C2=A0 =C2=A0 = =C2=A0 =C2=A0=C2=A0],

=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0"translations" : [
=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 "translations/en.json"
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 ]

=C2=A0 =C2=A0 }

<= div>css/login-override.css:

=C2=A0 =C2=A0 .login-ui .login-dialog .logo {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 background-image: url('app/ext/s= ome-unique-namespace/resources/your-logo.png');
=C2=A0 =C2= =A0 }

translations/en.json:

=C2= =A0 =C2=A0 {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 "APP" : {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 "NAME" : "Na= me of Your Choice",
=C2=A0 =C2=A0 =C2=A0 =C2=A0 }
= =C2=A0 =C2=A0 }

And then "resources/your-logo= .png" as well.

Once all that is zipped togeth= er and dropped into GUACAMOLE_HOME/extensions/ as a .jar file, it will auto= matically be loaded by Guacamole when the webapp starts. The custom CSS wil= l be appended to the existing CSS, overriding the original styles, the cust= om translations will be overlaid on the existing translations, overriding o= nly the strings you specify, and the custom logo will be served dynamically= from within a directory named after your chosen namespace. You'll prob= ably want to make other changes to the CSS, especially if your logo has a d= ifferent aspect ratio, but this is a start.

Other = than overriding the CSS, there's really not much programming involved; = it's a matter of adding whatever files you need to override what you= 9;re looking to override, and then declaring those files within "guac-= manifest.json":


- Mike


--001a1149b0a423102f05468b2626--