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 C0AE8200C8C for ; Tue, 6 Jun 2017 19:46:34 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BF2F6160BD3; Tue, 6 Jun 2017 17:46:34 +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 0F877160BB7 for ; Tue, 6 Jun 2017 19:46:33 +0200 (CEST) Received: (qmail 30976 invoked by uid 500); 6 Jun 2017 17:46:33 -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 30966 invoked by uid 99); 6 Jun 2017 17:46:33 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jun 2017 17:46:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id CE70FC00B6 for ; Tue, 6 Jun 2017 17:46:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.314 X-Spam-Level: ** X-Spam-Status: No, score=2.314 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 6hM1-5tOsx0c for ; Tue, 6 Jun 2017 17:46:30 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 86DFA5FDB7 for ; Tue, 6 Jun 2017 17:46:30 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id E83E047D6EAFF for ; Tue, 6 Jun 2017 10:46:29 -0700 (MST) Date: Tue, 6 Jun 2017 10:31:11 -0700 (PDT) From: santino83 To: user@guacamole.incubator.apache.org Message-ID: <1496770271373-1060.post@n4.nabble.com> Subject: guacamole-auth-cas-0.9.13 Session not handled correctly after login MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 06 Jun 2017 17:46:34 -0000 Hello, I need to use CAS for authentication, so I've used the new auth-cas extension. It works, meaning, authentication against CAS is done successfully and user got authenticated. However, web interface breaks, I mean that some functionalities don't work. One step back: Configuration: guacamaole-client 0.9.13 + auth-jdbc-postgresql extension + auth-cas extension I need jdbc to manage connections via graphic interface and other stuff. Well, following the manual I got the following scenario: - user go to guacamole webpages - auth-cas redirect user to Cas login page - user does login using cas, cas redirect to guacamole endpoint - guacamole validates user tickets against cas - user is logged in in cas after that, jdbc module looks in the database for a user matching the cas user, searchs for availabel connections, and so on. All works, or seems so. After login, if you try to open "Settings" menu (user personal setting), nothing happen ( a gear loading 4ever): looking at the console, I could read: /api/session/data/cas/self/USER_ID_LOGGED?token=.... with status 404, response: "no session associated with authentication provider cas". And so on for other apis, like session/data/cas/users, session/ext/cas... etc I don't know why it happens, I think that auth-cas ext is missing of something useful, like UserContext or something like this, but I didn't understand well how authentication and security framework work, so I wasn't able to find a solution to my problem. The only way I found as workaround was editing CASAuthenticationProvider.java and changed the provider identifier from "cas" to "postgresql". Everything now seems to work, but it is just an horrible workaround If someone could tell me how I could make a better solution, I'll be happy Thanks -- View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/guacamole-auth-cas-0-9-13-Session-not-handled-correctly-after-login-tp1060.html Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.