[jira] [Updated] (GUACAMOLE-793) CAS Provider returns Group - like LDAP Provider
[ https://issues.apache.org/jira/browse/GUACAMOLE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Jumper updated GUACAMOLE-793: -- Component/s: Documentation > CAS Provider returns Group - like LDAP Provider > --- > > Key: GUACAMOLE-793 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-793 > Project: Guacamole > Issue Type: Improvement > Components: Documentation, guacamole-auth-cas >Affects Versions: 1.0.0 >Reporter: David Young >Assignee: Mike Jumper >Priority: Minor > Labels: features > Fix For: 1.3.0 > > > This Improvement would reduce admin for those who use CAS for authentication > with a database provider that will be using Groups to mange connections, if > Groups could be > used somehow. > One possibility... > CAS Servers could be configured to return a Group name that matches a > Group in the database. > In this wishful scenario the CAS provider would then treat the Group name in > the same way the LDAP Provider now appears to be doing with the resolution > of issue 715. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-793) CAS Provider returns Group - like LDAP Provider
[ https://issues.apache.org/jira/browse/GUACAMOLE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Jumper updated GUACAMOLE-793: -- Fix Version/s: (was: 1.2.0) 1.3.0 > CAS Provider returns Group - like LDAP Provider > --- > > Key: GUACAMOLE-793 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-793 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-cas >Affects Versions: 1.0.0 >Reporter: David Young >Priority: Minor > Labels: features > Fix For: 1.3.0 > > > This Improvement would reduce admin for those who use CAS for authentication > with a database provider that will be using Groups to mange connections, if > Groups could be > used somehow. > One possibility... > CAS Servers could be configured to return a Group name that matches a > Group in the database. > In this wishful scenario the CAS provider would then treat the Group name in > the same way the LDAP Provider now appears to be doing with the resolution > of issue 715. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-793) CAS Provider returns Group - like LDAP Provider
[ https://issues.apache.org/jira/browse/GUACAMOLE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Couchman updated GUACAMOLE-793: Fix Version/s: 1.2.0 > CAS Provider returns Group - like LDAP Provider > --- > > Key: GUACAMOLE-793 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-793 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-cas >Affects Versions: 1.0.0 >Reporter: David Young >Priority: Minor > Labels: features > Fix For: 1.2.0 > > > This Improvement would reduce admin for those who use CAS for authentication > with a database provider that will be using Groups to mange connections, if > Groups could be > used somehow. > One possibility... > CAS Servers could be configured to return a Group name that matches a > Group in the database. > In this wishful scenario the CAS provider would then treat the Group name in > the same way the LDAP Provider now appears to be doing with the resolution > of issue 715. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GUACAMOLE-793) CAS Provider returns Group - like LDAP Provider
[ https://issues.apache.org/jira/browse/GUACAMOLE-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Young updated GUACAMOLE-793: -- Fix Version/s: (was: 1.2.0) (was: 1.1.0) > CAS Provider returns Group - like LDAP Provider > --- > > Key: GUACAMOLE-793 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-793 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-auth-cas >Affects Versions: 1.0.0 >Reporter: David Young >Priority: Minor > Labels: features > > This Improvement would reduce admin for those who use CAS for authentication > with a database provider that will be using Groups to mange connections, if > Groups could be > used somehow. > One possibility... > CAS Servers could be configured to return a Group name that matches a > Group in the database. > In this wishful scenario the CAS provider would then treat the Group name in > the same way the LDAP Provider now appears to be doing with the resolution > of issue 715. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
