How to set password in community version of Memgraph? - memgraphdb

How can I set the password for a non-enterprise instance of Memgraph? I'm using community edition. I'm not looking for role-based access control. I'd just like to have at least some level of protection.

Basic authentication is supported in the non-enterprise version.
You can create a password-protected account with the following query:
CREATE USER user_name [IDENTIFIED BY 'password'];
For example:
CREATE USER kwriter IDENTIFIED BY '8LJBhbu26d';

Related

How to view if an account is enabled/disabled, locked/unlocked in LDAP ODSEE

I am trying to modify accounts in LDAP(ODSEE) from SailPoint. When I view the attributes of the account in LDAP using a browser, I don't see any attributes that suggest if an account is enabled or disabled.
How can I find out an attribute of an account that carries information as to whether an account is enabled/disabled, locked/unlocked?
Do I then update my provision policy in SailPoint to include these attributes and update the values to perform the operation in LDAP?
I am fairly new to this and I am stuck so any help would be immensely appreciated.
The attribute used traditionally to lock account in Oracle is nsaccountlock, ns stand for netscape, check if this attributs exists in your ldap Schema, and create it otherwise.
src: https://docs.oracle.com/cd/E19225-01/820-6551/bzaoe/index.html

Block users from logging in using their database accounts

I have the following business problem to solve in a big legacy application written in PL/SQL and Oracle Forms 6i:
Not allow users to log in using their database accounts.
The whole application has around 50 users who use their database accounts. The audit department doesn’t allow that users know their database accounts passwords.
Rewriting the application to use a new user rights logic (using a table like USERS, only 1 database user, etc.) is out of the question as it’s too much work.
I thought about the following solution to use the existing database users:
Create a table USERS with usernames and new passwords, and somehow use a proxy user. In a package the application will check if the provided password is in line with the table USERS, and then connect as 1 of the 50 database users – so all application logic and user rights can stay the same.
But there is one problem with this workaround – you can’t use „connect” in a package. So I can’t use it.
begin
IF
p_in_user == USER2 AND p_in_pass == XXX
THEN
EXECUTE IMMEDIATE 'conn USER2/Password123'; -- doesn't work, using a proxy neither
END IF;
END;
Does anyone has any ideas?
The audit department doesn’t allow that users know their database accounts passwords
You can use encripted passwords.
Oracle allow to use encripted passwords through profile settings.
You can use a function to encript a clear password:
the clear password is given to end user
and on oracle database the user account is created/changed with the encripted password.
The user use his/her clear password to login and during login Oracle conver this to a encripted password for authentication.
Please confirm is this solution is ok, so I can post an example.

How to disable individual authentication in MVC Application

I am editing a template with authentication enabled in MVC with OWIN. I want to disable the authentication in the template and use an oracle db in the server to login the users. I searched on how to disable the authentication but found no result. I don't have option for registration. The user should be logged in if the user name and password is in the db.
There might be some confusion.As far I can understand from your question you want to remove authentication because you want to use oracle authentication. But, You can keep your authentication module and use oracle db no problem. If you are using Microsoft Identity check here and here. Things might have changed a bit.
You have to implement your for Oracle:
User (Microsoft.AspNet.Identity.IUser),
Role (Microsoft.AspNet.Identity.IRole)
UserStore (Microsoft.AspNet.Identity.IUserStore)
UserManager (Microsoft.AspNet.Identity.UserManager)
RolesStore (Microsoft.AspNet.Identity.IRoleStore)
RoleManager (Microsoft.AspNet.Identity.RoleManager)

How can I get password of logged in user in Dynamics CRM on prem?

I know how to grab guid and User Name of current logged in user in Dynamics CRM 2016 on prem. But I also need to grab the password for some business reason and pass it to another application for managing documents of the user.
What I have searched I find only to get the id and user name of the user but nothing find about the password of the user. I need to know how can I get the password of the current logged in user. Any idea/suggestion will be helpful.
You can't - unless the user gives it to you.
Passwords are handled by the authentication layer (Windows Integrated or ADFS) and CRM has no knowledge of the user's password. I do not believe Active Directory (or any other LDAP service on which ADFS might use) would allow you to read a user password.
In Server Side Sync a user may provide their password to CRM for Exchange authentication BUT that password cannot be read by anything other than the CRM platform (and they are encrypted in SQL.) You will not be able to read that password using code or SQL.
I do believe CRM On-Premise utilizes Active Directory. AD passwords are stored using non-reversible encryption, so you wont be able to get that in a readable format unless you enable reversible encryption, which i'd not advise doing for security reasons.
There are some steps mentioned to set up single sign on for sharepoint integration, this might help your cause.
Reference : https://sharepoint.stackexchange.com/questions/19662/how-to-set-up-single-sign-on-for-sharepoint-integration-in-crm-2011

Can't change passwords for technical users

I have a number of technical users on this system which was recently upgraded to SQ 5.2. The system uses LDAP authentication for normal users. When I try to change the password for a technical user, I get this:
Password cannot be changed when external authentication is used
I've also tried deleting the user, then re-creating it with the new password. That attempt gives the same error message.
I've made sure that the affected users are listed in sonar.properties, for sonar.security.localUsers.
This is planned to be fixed in version 5.3 : https://jira.sonarsource.com/browse/SONAR-7036

Resources