Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved PowerServer MSSQL SERVER Single Sing ON.

  1. Issue
0
Votes
Undo
  1. Andres Slachevsky
    Andres Slachevsky
  2. PowerBuilder
  3. Friday, 16 March 2018 12:44 PM UTC

PB12.5

Appeon 2016

The current application authenticate the user using SSO with Windows Active Directory

Most of the triggers and many PB code and Store Procedures use the user connected to perform some operations and save audit trail.

there are more than 1000 users

all the Users will be connected to the Entreprise Network no external users for the current application are expected.

checking the dynamic Database Connection does not solve the problem cause the users have only the NT authentication not a DB authentication.

Any way allow a Dinamic Database connection with SSO?

or the only solution is to change the to  DB authentication to the users and have 2 passwords?
Changing the code to not use a Dinamic Database connection is not a solution cause are many non PB application that use the same triggers and procedures and some external real time auditing that use the user connected information.

using Appeon users does not solve the DB connection issue

Please Help

 

  1. PowerServer
SQL Native client connection in runtime
Datetime field overflow when using SQL native driv...
Responses (2)
Govinda Lopez @Appeon
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Friday, 23 March 2018 15:49 PM UTC
  2. PowerBuilder
  3. # 1

Hi Andres,

 

Maybe Chris Pollac's Framework is what you are looking for: https://sourceforge.net/projects/stdfndclass/files/Applications/WebService/LDAP

​

 

Regards,

Comment
There are no comments made yet.
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Friday, 16 March 2018 20:01 PM UTC
  2. PowerBuilder
  3. # 2

Hi Andres,
first off, enable Windows authentication from your MS IIS server in order to use MS AD domain identities.
Now, the "Dynamic Database Connection" flag for the MSSQL datasource will allow you to set the LogID and LogPass properties of the transaction object.
So, you can now SSO to the application and establish different connections from different users.
Of course, set the pool size down to 1, since the default min/max (10/100) values are meant for DB connection pooling ans would waste lots of resources.

Instead, if you are running a JEE application server (JBoss, WAS, WL...) the dynamic DB connection setting does not work, but you can workaround using Java helper classes for your DB.

Cheers,
Marco

Comment
Andres Slachevsky
  1. Andres Slachevsky
  2. Monday, 19 March 2018 11:36 AM UTC
Hello Marco,



The issue is that the customer is asking if they can keep the SSO to the database server not the application itself.



i will try the steps you wrote and let you know

  1. Helpful
Andres Slachevsky
  1. Andres Slachevsky
  2. Tuesday, 20 March 2018 13:50 PM UTC
Hello Marco.



i have try your solution.



My problem remains the same the database server (MS SQL SERVER) is set to windows authentication so there is no user/password to set the dataSource and if i check the Dynamic Database Connection it requires a User / password that i don't have



i try to set the Other Options with : integratedSecurity=true or TrustedConnection=1 or Secure=1 



and the problem remains i recieve and error on the login to the database during connect;

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.