OpenLdap multiple administrators under the same DC - openldap

Im currently playing with openldap (+phpldapadmin)
Howver i dont know how to create a new adminuser for ldap.
Tried to clone the CN=admin as another name, but in that case in phpldapadmin.
I can login with that new account however i got the following error
This base cannot be created with PLA. in the tree view.
Sadly nor search is possible with that.
Is there any tip howto create multiple CN user under the DC=example,DC=org ?

Related

Access accdb MsysObjects permission

Hello to forum from a part time occasional user of MS Access 2010:
Trying to get permission to allow a third party application read MsysObjects which in turn will allow it to save a copy of the table relationship window in a form that will allow the layout to be recovered when it crashes (frequently - and is a known irritation/bug).
Have tried the method suggested in quote from this forum [HansUp] without success - including substiting this DAO line for the last ADO line following advice on a different forum:
dbEngine(0)(0).Execute strDdl, dbFailOnError
Since your db is ACCDB format, you will be working as user Admin. You can confirm that point in the Immediate window. (Go there with Ctrl+g)
? CurrentUser()
Admin
Since Admin doesn't have read (SELECT) permission on MSysObjects, execute a DDL statement to give Admin that permission.
strDdl = "GRANT SELECT ON MSysObjects TO Admin;"
CurrentProject.Connection.Execute strDdl
Advice from yet another forum to import or export to fresh blank accdb gives no result as permissions are still not available.
All this is beyond my pay grade so any advice welcome.

Allow Meteor Accounts to have multiple users with the same email address

I'm building a Meteor app where I don't care if two people have the same email address because I'm using the username as login key.
I've been searching for a way to setup Meteor Accounts (accounts-password) to make this possible but I couldn't find any resource.
Is it even possible ? Should I roll my own registration mechanism just for that small difference ?
In account-base.js, this index is set
Meteor.users._ensureIndex('emails.address', {unique: 1, sparse: 1});
This is what set the behaviour. We need to drop that index. Looking at the doc, i see that
Meteor.users._dropIndex({"emails.address": 1});
will do the trick, BUT, I am new i Meteor, so I don't know where to put this and if this is the best approach.
I put it in a server file and it worked fine... but research more

How can I specify which shiny account to use when deploying?

I just want to ask about shiny accounts, I have two shiny registered accounts and now when I want to deploy I saw error like this
Do you want to proceed with deployment? [Y/n]: y
Error: Please specify the account which you want to deploy the application to (there is more than one account registered on this system).
So my question is how to specify the account that I want to used it in deploy application, when I just tried to run like this
shinyapps::setAccountInfo(name='xxxx',
token='13SDADASDSADAD9FCCEC48C016D5D97',
secret='863pLqbfaxeradasdafasfsadxzadadXgi2NfXh')
setwd('D:/ASD/test')
library(shinyapps)
deployApp()
I still got same error.
Go to top menu your Rstudio-> Tools-> ShinnyApps -> Manage Accounts
There are mainly two different parameters to set up: the name and the account, each used in a different function. Previous answers did not make this altogether clear, so let me add explanations.
Step 1: Set name via setAccountInfo():
Go to https://www.shinyapps.io/admin/#/dashboard and get your personal name/token/secret, e.g. "myName" / "myToken" / "mySecret". You'll need all three to authorize your account.
library(shiny)
library(rsconnect)
rsconnect::setAccountInfo(
name = "myName",
token = "myToken",
secret = "mySecret")
You're now ready to deploy your apps. If you have a single account, that is all you need to do. But with multiple accounts, you also need to set the account explicitly in the deployApp() function:
Step 2: Set account via deployApp():
setwd("my/local/dir/") # or set the full path below
rsconnect::deployApp("myAppNameOffline",
appName = "myAppNameOnline",
account = "myname")
Bonus: If you set option appName explicitly your app can have a different name online as it does offline, e.g. "myapp-version-999" can simply become "myapp" online.
If you have multiple accounts on shinyapps.io, specify the account name while deploying the app
get a list of accounts
deploy it to the desired account
accounts(server = NULL)
shinyapps::deployApp('./AppPath',account='second_account_name')
Use the following command to remove all the accounts
removeAccount("user")
Then, add reconfigure your rsconnet using the follwoing functions
rsconnect::setAccountInfo(name, token, secret)
In RStudio go to: Tools => Global Options => Publishing
and remove useless users.

Super user error when importing mysqldump?

I've done a mysqldump from our Drupal6/CiviCRM4 Civi DB and am trying to import it into a Drupal7/Civi4 dev install, but keep getting "ERROR 1227 (42000) at line 369: Access denied; you need the SUPER privilege for this operation"
From what I can tell, user has correct permissions as indicated via site's cpanel, all appears correct in the import command. I've not come upon this error before doing similar proceedures on other installs. Help please?
It could be one of a couple of things.
First, if you have MySQL version before 5.1.6, you'll need the SUPER permission no matter what:
http://wiki.civicrm.org/confluence/display/CRMDOC/CiviCRM+MySQL+Permission+Requirements
However, since it has been running fine and you're just trying to import the dump file, I think it's probably that your dump file has functions where the definer is set as the database user for the old site (let's say "foo#localhost"). You aren't allowed to set the definer as someone other than yourself without the SUPER privilege. If the new site has a different user (maybe "bar#localhost"), you're acting as "bar#localost" trying to set a function defined by "foo#localhost".
In your dump, you'll probably see something along the lines of
CREATE DEFINER=`foo`#`localhost` FUNCTION ...
You can do one of two things:
have both databases use the same database user account, or
edit the dump file to replace the old user name with the new user name everywhere it occurs.
You should also be aware that "foo#localhost" and "foo#%" are separate users, even if they have the same name and password.
A Drupal/CiviCrm database uses triggers. The SUPER privilege is needed to recreate the trigger when you import the database. If you've restricted your standard user's privileges to those needed while running Civi, you can create a new MySQL user just for the import and grant that user ALL privileges on the database(s). After the import is complete, remove the user with elevated privileges.

Permission error when trying to add or edit addresses (e.g. Customer Address)

I am trying to do some development to the LogisticsPostalAddress form that is used on forms where an address is modified/added. When trying to add an address (e.g. to an existing Customer) I get the error.
You are not authorized to access table ‘Shipping carrier’ (ShipCarrierAddress). Contact your system administrator.
I have scoured the user permissions and cannot find a way to give permission to this table. I would think that adding an address is a basic function, so can not figure out why I can't.
Thanks,
Kevin
What role is your user assign to? Are you sure users in that role should be able to add addresses to the customer? If yes, here is how you can add permissions to the ShipCarrierAddress table:
With admin user, open development envionrment (Ctrl + Shift + W from
running Ax, or run "ax32.exe -development" from command prompt)
In the AOT, go to Security > Roles. Find the role your user is assigned to.
Exapand the Role > Permissions > Table, add new table and set table name to ShipCarrierAddress and EffectiveAccess (in your case
you want to insert, thus set to Create)
Save the role, and compile the role (not sure if compile is mandatory)
Start a new Ax instance with the user with limited permissions and verify you have access.
I turned out it was an issue with the installation of the lab.

Resources