Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.ms-access > #12642 > unrolled thread

Providing credentials to Access at run time to connect with linked sharepoint lists

Back to article view | Back to comp.databases.ms-access

Contents

  Providing credentials to Access at run time to connect with linked sharepoint lists bobalston@gmail.com - 2017-06-26 21:17 -0700
    Re: Providing credentials to Access at run time to connect with linked sharepoint lists Ron Weiner <rw@domain.com> - 2017-06-27 10:05 -0400

#12642 — Providing credentials to Access at run time to connect with linked sharepoint lists

I am looking for a way to provide login credentials for SharePoint lists that are linked to by an Access front end.

Normally that is straightforward.

My issue is that I want to prevent the user from being able to access the sharepoint lists directly in Sharepoint.   Normally they would have that capability but I try to hide the lists in a subsite and tell them to never even try.

So my idea is to set permissions to the updated tables, now SharePoint lists to a unique user ID and then provide the credentials at run time of the Access FE so that the user who is authorized to run the Access front end can access the connected tables/lists but cannot do so without Access front end running.

And, of course, it would be great if the "scope" of that connection is limited to the Access program, so that the user could not just run the Access front end, connect to the sharepoint lists, then open up sharepoint via a browser and manipulate the lists.

Needed for the high security of this app.

Solution?

Bob

[toc] | [next] | [standalone]

#12644

on 6/27/2017, bobalston@gmail.com supposed :
> I am looking for a way to provide login credentials for SharePoint lists that 
> are linked to by an Access front end.
>
> Normally that is straightforward.
>
> My issue is that I want to prevent the user from being able to access the 
> sharepoint lists directly in Sharepoint.   Normally they would have that 
> capability but I try to hide the lists in a subsite and tell them to never 
> even try.
>
> So my idea is to set permissions to the updated tables, now SharePoint lists 
> to a unique user ID and then provide the credentials at run time of the 
> Access FE so that the user who is authorized to run the Access front end can 
> access the connected tables/lists but cannot do so without Access front end 
> running.
>
> And, of course, it would be great if the "scope" of that connection is 
> limited to the Access program, so that the user could not just run the Access 
> front end, connect to the sharepoint lists, then open up sharepoint via a 
> browser and manipulate the lists.
>
> Needed for the high security of this app.
>
> Solution?
>
> Bob
>
> ---
> This email has been checked for viruses by AVG.
> http://www.avg.com

Let me first say I have never worked with SharePoint, and I am assuming 
that that you will link the Access front end to the share point list's 
and use them in Access as though they were linked tables.  If 
SharePoint does not work this way you can stop reading here.

I have used Sql Server tables linked to Access front ends by encrypting 
the Username and Passwords and storing them in an obfuscated Access 
table in the front end.  Then at runtime programmatically link Access 
to the back end tables using the credentials stored in the Access 
obfuscated tables after decrypting them.

You could also create custom properties in the Access front end that 
contained the Encrypted credentials.  This would be slightly harder for 
the average user to discover, but for the really determined, I think 
you are pretty much screwed.

There are all sorts of other problems that you'll have to work out like 
making sure that those linked tables are removed from the front end as 
soon as you are done using them.  Consider the motivated user that 
quits Access as soon as the app created the links, and reopened the 
front end and started searching for the linked tables.  At this point 
s/he would have unfettered access to everything.  Also you will need to 
insure that the user had no access to the Encrypt/Decrypt or Property 
get code.  So now you are looking at distributing MDE's or ACCDE's.

I you are wanting to protect against curious snoopers then this will 
probably work well enough.  However if the stuff you want to keep 
secure is something like the nuclear launch codes, Access is not a good 
platform on which to base your application.

Rdub

[toc] | [prev] | [standalone]

Back to top | Article view | comp.databases.ms-access

csiph-web