1.No action
2.Perform this action this time
3.Trust the signer to perform this action of this Notes session
4.Start trusting the signer to perform this action
Some users will appear in the "Enforce Security Alert" window when using NOTES. At present, users are asked to select item 4 by themselves, but this problem often occurs.
Is there a way to solve this problem at once without letting the user personally operating?
Sorry, only the Chinese version of the screen
You can add a Security Settings policy document to the Domino Directory that contains entries for a standard Execution Control List. The Domino Admin help database explains this in more detail.
Related
Just getting around to setting up some more detailed reporting in our OneLogin setup, and I'm not sure how to go about the title to this question. How would I create a new notification to alert us when a user account gets reactivated in any way and by whom it was done by?
This has been somewhat helpful, but I feel like there are more OL database values that can and/or need to be used to get what I need.
In your administration panel there is a tab for Notifications under the Activity tab. You are able to configure a email notification whenever an account is reactivated.
Upon getting the email you can log into your administration panel and view the user profile within the account to view who made the changes.
I am not an expert on the UI side of Onelogin, but I work on the engineering team. There may be an easier way to do this, but the functionality is there.
Writing this post because I could not locate much content on troubleshooting specifically for connecting a Salesforce Sandbox as a connected Zapier account.
First troubleshoot issue is that you must select that you wish to connect to a sandbox account from the "advanced options" feature by doing as follows
1) From Zapier dashboard, nagivate to "Connected Accounts"
2) use the search bar with text "add new account", to find Salesforce, selecting this will open a pop-up, you must select "advanced options" and then select "sandbox, instead of production.
Secondly, I had an issue with Privilege error and could not locate a soluton on the forums. Here was my solution -
1) Zapier would constantly default to connecting to an old sandbox. To cause Zapier to allow me the option of selecting a new sandbox, I had to log out of both, Zapier and all Salesforce sandboxes and Productions.
2) Once I logged onto the desired sandbox, I had an error stating I did not have the privileges to perform my requested action, despite being an admin. It turned out the new custom objects I had made in Sandbox did not have any users down as having read/write authorization and even though it was only two custom objects, this was enough to trigger a rejection for the whole Zapier-Sandbox account linking. I made a permission set for the new objects, assigned them to all users and allowed all read/write access (note, use more appropriate security settings for your organisation). This finally fixed the issue and I could now test zaps on my Sandbox.
First troubleshoot issue is that you must select that you wish to connect to a sandbox account from the "advanced options" feature by doing as follows
1) From Zapier dashboard, nagivate to "Connected Accounts" 2) use the search bar with text "add new account", to find Salesforce, selecting this will open a pop-up, you must select "advanced options" and then select "sandbox, instead of production.
Secondly, I had an issue with Privilege error and could not locate a soluton on the forums. Here was my solution -
1) Zapier would constantly default to connecting to an old sandbox. To cause Zapier to allow me the option of selecting a new sandbox, I had to log out of both, Zapier and all Salesforce sandboxes and Productions.
2) Once I logged onto the desired sandbox, I had an error stating I did not have the privileges to perform my requested action, despite being an admin. It turned out the new custom objects I had made in Sandbox did not have any users down as having read/write authorization and even though it was only two custom objects, this was enough to trigger a rejection for the whole Zapier-Sandbox account linking. I made a permission set for the new objects, assigned them to all users and allowed all read/write access (note, use more appropriate security settings for your organisation). This finally fixed the issue and I could now test zaps on my Sandbox.
I want to be able to make it so a registered user can only be logged into the DNN site from one device/browser at any one time.
I understand that the DNN core doesn't support sessions but does have a a users online table which is checked by the scheduler, however i have been unable to find anything available to use this method.
The main purpose is to stop a paid user from sharing their login details with multiple people and thereby diluting the potential revenue to the site. I would think this was not a unique use case and someone must have dealt with this previously.
Open to any and all ideas including commercial modules.
I suppose that you could create a custom login module, and reject logins from a user who appear as active in the UsersOnline table.
I haven't looked around to see what methods are available, but the old usersonline module should provide some hints.
We are setting up a new application framework and we are wondering the best practices for setting up database security for our users. In our old framework, there was a user logon process and once the user was logged on, the framework controlled what forms and menu options a user was permitted to. All users accessed the database with the same user account.
The disadvantage to this approach is that you cant use SYSTEM_USER to find out who is making a particular database request.
The new framework will still have a logon form and it will control what menu options a person can access. Should we be setting up a database user account every time a new user is added to our application? Would this cause any licensing concerns since you cant use connection pooling?
It won't cause licensing issues, but it will generate a large number of connections which may cause performance issues.
A better solution would be to add a parameter to your stored procedures to pass in the UserID of the current user so that it can be logged.
If passing in the parameter is undesirable, you can put the current user in CONTEXT_INFO(), or if you are using SQL 2016, SESSION_CONTEXT() and log it from there. https://www.mssqltips.com/sqlservertip/4094/phase-out-contextinfo-in-sql-server-2016-with-sessioncontext/
Scenario:
I get a mail from Foo Bar about a problem. I add the issue to Bugzilla and would like Foo Bar to be the reporter of the issue so it will be possible to do searches on issues reported by this individual etc.
I understand that I most likley will have to create dummy users for every reporting person since Bugzilla only works with the users in it's system. But if I could live with that, would it be possible to accomplish this?
The only way to do it would be to actually log in as the dummy user when reporting the bug. (Or if you have permission, use the impersonation feature.)
To make the reporter field editable on the bug submission form, you'd have to edit the source code.
The impersonation feature is documented here. Quoting briefly:
You may start a session by going to
the Edit Users page, Searching for a
user and clicking on their login. You
should see a link below their login
name titled "Impersonate this user".
Click on the link. This will take you
to a page where you will see a
description of the feature and
instructions for using it. After
reading the text, simply enter the
login of the user you would like to
impersonate, provide a short message
explaining why you are doing this, and
press the button.
There is no way in the web interface to do this.
It can be achieved via the XMLRPC mehtod only, but this is not suitable for most use cases:
bugzilla.changeAssignment($bugid, { reporter => new#reporter.com },
$username, $password);
Source: https://bugzilla.redhat.com/show_bug.cgi?id=432238