Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    dynamic credentials - oracle builtin

    I'm using Oracle as my database. I used the Oracle example and all is working so far. What I need to do is to be able to fill in the userid/pw dynamically. Currently I have to hard code them using sql.Oracle.driver.user and sql.Oracle.driver.password. I also notice a parm called sql.Oracle.interface.credentialsInURL.

    In the example using HSQ, there is something called HSQLServletContextListener that allows you to do just this. Is there something like this available for the Oracle builtin?

    thanks

    #2
    How dynamic are these credentials, per deployment or are users actually entering database passwords in the UI?

    Per-deployment credentials are typically handled with Ant scripts and the like that use different versions of server.properties to handle different scenarios.

    Per-user is a little harder. Are we talking about different users concurrently connecting to the database with different credentials? One consequence is that connections cannot be pooled (except on a per-user basis).

    Comment


      #3
      Per-user.. They are entering userid/pw via a UI.. and yes they are concurrently connecting to the database with different credentials.


      Originally posted by Isomorphic
      How dynamic are these credentials, per deployment or are users actually entering database passwords in the UI?

      Per-deployment credentials are typically handled with Ant scripts and the like that use different versions of server.properties to handle different scenarios.

      Per-user is a little harder. Are we talking about different users concurrently connecting to the database with different credentials? One consequence is that connections cannot be pooled (except on a per-user basis).

      Comment


        #4
        Interesting. To do this today, you would:

        1. create a JNDI DataSource configuration dynamically as each user logs in (here "DataSource" means "JNDI DataSource" not SmartClient DataSource)

        2. use the server-side API DataSource.fromXML() to dynamically create SmartClient DataSources with the "dbName" setting matching the JNDI configuration you set up above.

        We could make this quite a bit easier (eg, a new API SQLDataSource.setJDBCUserName() / setJDBCPassword()) - if you want to avoid the rigmarole, consider Feature Sponsorship - this would be a relatively small job.

        Comment


          #5
          Would this something that could be included in smartgwtPro. I am actually in the process of purchasing a license. Also, how do I speak with one of the technical people. I am almost at the point of no return and need to make sure I understand what will stop working with the evaluation I'm using, etc.

          Originally posted by Isomorphic
          Interesting. To do this today, you would:

          1. create a JNDI DataSource configuration dynamically as each user logs in (here "DataSource" means "JNDI DataSource" not SmartClient DataSource)

          2. use the server-side API DataSource.fromXML() to dynamically create SmartClient DataSources with the "dbName" setting matching the JNDI configuration you set up above.

          We could make this quite a bit easier (eg, a new API SQLDataSource.setJDBCUserName() / setJDBCPassword()) - if you want to avoid the rigmarole, consider Feature Sponsorship - this would be a relatively small job.

          Comment


            #6
            Once you had sponsored it, it would be included with SGWT Pro (not sure if that's what you were asking?).

            You *are* speaking to a technical person ;) Take a look at this feature breakdown for details on which features come with which editions.

            Best thing is probably just to call in about buying Pro, getting this feature added, maybe adding support, and ask for a combined price.

            Comment


              #7
              I did not mean to imply that you were not a technical person, I meant how could I speak to one on the phone. I have been in contact with sales regarding buying a pro license. I did read over the feature breakdown and I am pretty sure the pro is what I need. I just wanted to go over a few items to make sure I understood everything.

              Originally posted by Isomorphic
              Once you had sponsored it, it would be included with SGWT Pro (not sure if that's what you were asking?).

              You *are* speaking to a technical person ;) Take a look at this feature breakdown for details on which features come with which editions.

              Best thing is probably just to call in about buying Pro, getting this feature added, maybe adding support, and ask for a combined price.

              Comment


                #8
                @Isomorphic,

                I have a need for this so that I can use mysql/postgresql auditing. Thus, I need to make a connection on a user bases. I would love to sponsor the features you described in "2" and would love to read more on how to dynamically create JNDI Datasources that you mentioned in "1"

                Regards,
                Mike

                Comment


                  #9
                  Information about sponsoring is here. Consider also a full Jump Start (described on same page) - we could provide a working starter application that demonstrates the complete technique (with or without adding this feature).

                  Comment

                  Working...
                  X