I have an Access 2010 database with linked tables that connect to a sql server database. I do not have the connections set as a trusted connection, instead I want the linked tables to connect to the sql server login and password I provide. For users who are accessing this over our network it is still prompting for the password even though it displays the login id. Is there a way to make Access save the password as well in Access?
I found that in order to save a password in the DSN, I had to create a File DSN and in that file I had to be sure to include a field for the password such as:
PWD=mypassword
But there is a risk of exposing the password in a file. Ultimately, we decided that it was better to make users enter the password, which will be prompted for on just the first time they try to get a result from a query or table after they open the Access database file.
Related
I need to import a sql. database to Wordpress through phpMyAdmin.
Anytime I want to create a new database this error happens (#1044 - Access denied for user 'xxx' to database 'zzz').
Thanks for your help.
You can check all privileges permission of database user and also check our sql file. May be mention there "CAEATE DATABASE '*******'" if you have that then you remove that. Most of this #1044 refer you to check your database user and permission of your database. I think this suggestion will help you.
As the others have mentioned, shared hosting environments generally don't allow you to create any arbitrary database name, sometimes you're limited to only one database and sometimes it has to be a subset of your username or something. If that's the case, you'll need to edit the .sql file to force it to use the database name you've been assigned.
If that's not the case, it's likely the user you are logged in as doesn't have the privileges to create a new database, so you'll need to log in as a user that does have privileges. Perhaps you're not logged in as the user you think you are. Note that the username and host value need to match, otherwise you could be logged in as the anonymous user instead of one that has permissions (for instance, if your user account is mia with host field 127.0.0.1 but you're logged in via the socket connection to 'localhost', it doesn't match.
I wanted to create a repository to store transformations and jobs in it. I don't want to install a heavy weight RDBMS, and since Kettle/Spoon can deal with SQlite3 Databases I thought, I could use a SQlite3 Database.
So I created a new database file using the shell and I used the Repository Manager to create a new database connection to this new database file.
It worked, no problem. It also doesn't matter which user password combination I use: the test is successful.
My connection details look like this:
All database tables seem to be in place:
But when I want to access the repository, I'm being asked for a password. I use admin:admin, but I'm getting this message:
I checked the r_user table in the database. I was considering, to change the password there, but I read here that the default password is admin.
I was also thinking, that it's the database user and password that is required, but since it's a sqlite3 DB there is no such thing as a user and password to access it.
Anyone can help, please?
It's a bit embarrassing, but I'm not sure for whom, but...
If you open up the repositories.xml in .kettle directory, you'll see this:
That's a version where I didn't supply a password for the DB User (not the repository user). In this case you see the text Encrypted in between the <password> tag.
If you delete this text (leaving the <password> tag empty) the connection to the repository works (with user admin and password admin for the repository connection).
If you specified a password for the DB connection the encrypted password is stored in the repositories.xml file. But it's also prefixed with Encrypted. If you delete the prefix and leave the encrypted password intact it also works.
Since it's a sqlite3 database it doesn't matter what's the password, though.
Hope someone else will find this helpful.
I have a NSF file which I want to decrypt so that it can be opened without password.
I have changed the encryption settings of the database to "Do not locally encrypt this database". Now I need to locally replicate this database, so that the new replica would be opened without password. Please let me know the correct procedure to achieve this.
Thanks in advance.
To access the NSF file through the Notes client the user will have to authenticate using a local ID file - regardless of whether NSF encryption is used.
The user will be asked for a password as soon as the client is opened, in this case when the user opens the NSF file.
To avoid the user being asked for a password, you can do one of the following:
Make sure the Notes client is already open, and a user logged in.
Use a user ID with a blank password.
Setup some kind of SSO, for example by using the same password used for Windows.
Bear in mind that IF the NSF file is encrypted, it should be encrypted using the same ID file later used to open it.
After setting "Do not locally encrypt this database" you only need to compact the database. Then the database is not encrypted with user's Notes-id anymore and others can open the database locally too.
You can compact your database right in Notes Client workspace:
Select the database
Choose File - Database - Properties
Click the "Info" tab.
Click button "Compact"
The data entry form in My DB 2010 will not allow anything to be entered. If I make DataEntry to YES, the from is blank. If I change it to NO, it displays the typing fields, but I cannot enter anything. I have also made Additions and Edits to YES.
The DB is linked to another DB stored in a network where I have only read only access. When I copy the DB from the network to my local machine and relink the tables, the data entry form works fine. I need this DB to work from the network.
You're using bound forms, which in a shared environment isn't best practice, but the root issue is that you only have read access to the back end database. You'll have to request read/write entitlements to the folder location that contains the back end database. Another option would be move the back end database to a new location where users do have read/write access. Lastly, you could always link the tables using an entitlement that does have read/write access.
I'm wondering how to solve the following issue:
I have a web asp.net app where Forms Authentification is used, connected to the Active Directory. Also, I have a connection string to MS SQL db in the web app, where one global user (with given privileges) is used. The problem is that when I want to store information about the user (e.g. data modification log) in database, I can only get the global user info provided in the connection string, not the real user who is logged in.
Is there any possiblity to log onto a web app with my personal credentials, after, use a global user credentials to connect into the database and pass my personal user credentials (but not as parameters in store procedure) that database will think that the user who is logged in is not the global user?
I assume, it might be only possible if I also create same users in the database and use Impersonalization?
Or any other possibillities?
Thanks in advance.
What are you doing to get the current user? Are you doing something like SELECT #user = SYSTEM_USER? This will obviously only return the user that you connect to SQL Server with.
I would rather keep to using a single SQL login that the application uses, but pass in the username when you are making changes, e.g. through a sproc or a table update:
CREATE PROCEDURE dbo.DoSomething
#id INT,
#username VARCHAR(50)
AS
-- Make your changes.
INSERT INTO dbo.[Audit] SELECT 'update', #id, #username
GO
In ASP.NET you can grab the currently logged in user through User.Identity.Name property of the page.
You could use a role within your database to handle permissions, and then get the users you need in a group in AD, and assign permissions to that AD group to access your database under the role you define. (This way you don't need to assign each user to your database as you create them).
You would then use windows authentication right the way through from your web site to the database, and have the user identity that you need for logging. (You'll need to set identity impersonate="true" in your configuration).
I would note that this is only going to work (easily) if your servers and your users are all on the same network.