• State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 96 subscribers
  • Views 6084 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Using DBBulkImport API with current JobServer user.

hleigh
over 8 years ago

I'm looking to use this Object API for the bulk import of thousands of 1IM object - however the SDK documentation only details a single initializer

Public Sub New ( _
	tableName As String, _
	connectionString As String, _
	dbFactory As IDbFactory, _
	authString As String _
)

Does anyone know of a way that this API can be used with the current Connection / User as would be available on the Job Server ?

I want to avoid having to provide the username / password in the authstring parameter - rather utilizing the existing connection.

Thanks
Parents
  • 0 over 8 years ago

    I see that you thought about the pro and cons and therefore I am relived. That was the only point I wanted to make.

    I just have one further suggestion. I am assuming that your are running on a version 6.x so, what you could do for the authentication string.

    If you want to avoid the use of a password in the authentication string, why not use one of the AD based authenticators. Drawback is, that the account your are testing this and the account the job service is running with, have to be present in the One Identity Manager database and have to be linked to a person.

    For example if you use the authenticator "Active Directory User account" your Authentication String would look like the following:

    Module=ADSAccount

    The permissions will be determined by the DialogUser set at the person.

    HtH

Reply
  • 0 over 8 years ago

    I see that you thought about the pro and cons and therefore I am relived. That was the only point I wanted to make.

    I just have one further suggestion. I am assuming that your are running on a version 6.x so, what you could do for the authentication string.

    If you want to avoid the use of a password in the authentication string, why not use one of the AD based authenticators. Drawback is, that the account your are testing this and the account the job service is running with, have to be present in the One Identity Manager database and have to be linked to a person.

    For example if you use the authenticator "Active Directory User account" your Authentication String would look like the following:

    Module=ADSAccount

    The permissions will be determined by the DialogUser set at the person.

    HtH

Children
No Data