Uploaded image for project: 'Apache Guacamole - Contributions'
  1. Apache Guacamole - Contributions
  2. GUAC-586

Decouple storage and authorization from authentication

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 0.9.8
    • Component/s: None
    • Labels:
      None
    • Sprint:
      DEV 2015-09-04
    • Story Points:
      8

      Description

      Guacamole's extension API requires that authentication providers provide their own configuration and connection storage.

      It would make more sense to decouple authentication from storage, and allow things like a MySQL backend to exist independently of authentication (which could leverage MySQL, LDAP, XML, etc. separately).

      Separating authorization from authentication would allow mechanisms to be used solely for identifying users, with the information regarding which connections they can access being stored elsewhere, possibly spanning different extensions.

      There should not be the restriction that only a single storage/authentication/authorization mechanism be used. They should be poolable - automatically working simultaneously and independently.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mike.jumper Michael Jumper
              Reporter:
              mike.jumper Michael Jumper
              Votes:
              5 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: