GitHub user necouchman opened a pull request:

    https://github.com/apache/incubator-guacamole-client/pull/182

    GUACAMOLE-363: Add support for SQL Server authentication

    This pull request implements a SQL Server (sqlserver) module for the JDBC 
authentication backend, allowing the Guacamole database to be hosted in SQL 
Server.
    
    I went the route of creating a guacamole schema and renaming the tables a 
bit - I have a feeling I'll end up changing that to be more consistent with the 
other modules, but SQL Server uses a default "dbo" schema that's just 
different, anyway, so I took a stab at it this way.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/necouchman/incubator-guacamole-client 
GUACAMOLE-363

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-guacamole-client/pull/182.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #182
    
----
commit 3b8c802e239645e4ff31f4b86b781f1da58d312f
Author: Nick Couchman <[email protected]>
Date:   2017-08-15T02:14:15Z

    GUACAMOLE-363: Initial commit of SQLServer authentication module for JDBC.

commit b95fb938e6edf89fff1252c1fa931dcea2d13374
Author: Nick Couchman <[email protected]>
Date:   2017-08-15T18:28:20Z

    GUACAMOLE-363: Fix up JDBC maps for proper SQL Server syntax.

commit c9d4adef7c493b675325fda5e8f4dff362185139
Author: Nick Couchman <[email protected]>
Date:   2017-08-15T21:03:25Z

    GUACAMOLE-363: Fix style, order, and batching in SQL Server schema scripts.

commit 765d0812c8386a7563ad7b4f75b5309c94e43ec9
Author: Nick Couchman <[email protected]>
Date:   2017-08-15T23:56:00Z

    GUACAMOLE-363: Fix encoding of SQL file

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to