I am the administrator of Netsuite Account. I have installed suite bundle. I have created 5 employees under the same role. But i want restrict to access the suite bundle for one employee. 4 can access the netsuite bundle. Remaining one should not access the suite bundle.
How to do that?
i am facing similar issue asked in the post
Can't access Restlet File in Netsuite?
But i asked in different way.
Related
Hi I'm currently trying to deploy Watson Studio Lite but it will not allow me to do this without a resource group. And when I'm trying to create a resource group I do not have permission to do so.
Could someone please advise? IM taking the IBM data science certification online with Coursea and their instructions are either dated or not specific to my issue.
when creating a new IBM Cloud account, a default resource group should be created automatically. Unfortunately you will not be able to create another one without upgrading to a paid account. There are two options:
You can chat with support in the support center.
You can create a new account with a different email address.
I wanted to try provisioning my app resources in Azure using the TeamsToolkit, but it fails creating the resource group since my company requires 4 tags to be added.
Is there a way to tell the toolkit to either add those tags or create the resource group myself and make it aware of it?
I tried doing with Teams Toolkit and didn't find any option to configure the resources (choose existing or setup policy).
Following the doc also there's no mention about doing such - Deploy your app to azure and even on the market place it is not
mention that we can configure it.
I have google cloud build set up, and I'd like t away to make the builds publicly visible, to use in an open source project, a bit like how TravisCI and CircleCI offer - see an example below:
https://travis-ci.org/wagtail/Willow/pull_requests
Is this possible?
Can you make it possible to inspect a build to a non-signed in user?
A solution could be to use Google Identity and Access Management to grant the Cloud Build Viewer role to allUsers. However, this cannot be done at the moment.
The idea is to give the cloudbuild.builds.get and cloudbuild.builds.list permissions to everyone on the internet, which would allow them to call those Cloud Build API methods that require these permissions. You can grant roles to Google Accounts or Groups, Service accounts or G Suite domains, but not to everyone.
You can find detailed instructions to grant roles through the GCP console in the Cloud Build documentation.
I am new to SonarQube and trying to setup up a proper access control, with requirements as follows:
We have a few project areas, each area should have someone able to
manage their area, such as creating new projects and manage the
boards, not sure exactly what. This is something like project area
administrators.
A few administrators can do anything.
Integrate to AD
A few questions:
In a few places like this link: http://www.sonarsource.com/products/features/security/, I see this role based method, but I can't find these default roles, "SonarSource products come with three project-specific roles – project administrators, project users and project code viewers" anywhere in the system. Right now, I am using the community edition I guess without a license. Is there any more detailed document on that?
I kind of understand the default Global Permissions and Project Permissions. In my case, shall I create e.g. three groups in AD, sonar-administrators,sonar-project-administrators, sonar-users to map to the default groups?
I notice the following: right now I don't have the above AD groups, when I integrate to AD, I can login with my domain id/password, but once logout/in, the group information I added to the local user gone. I guess it sych with AD. So to use AD, I have to create these groups in AD?
Jirong
Access control in SonarQube is managed through Global Permissions and Project Permissions. Each permission can be granted to user(s) and/or to group(s). The documentation you pointed at is quite outdated, read the Authorization page for the most up to date details.
AD/LDAP integration is a different topic, documented here. With group mapping, group membership stays managed in AD but will be replicated in SonarQube when users log in (the AD groups must first be created in SonarQube with the same name).
To your example: if AD users belonging to group foo deserve to administer your SonarQube, just create group foo in SonarQube, and (in the Global Permissions settings) give Administer System permission to group foo.
I have a web application developed with Struts2, JSP, JPA, Spring and MySql. I want to move this application to Amazon Cloud. I have not done a cloud deployment before or know how to do it.
Can anyone help me on a step by step process or a procedure to follow or a document that will guide me in doing this. Thanks for your help.
Upload your project's .war in elastic bean stalk and deploy project.
The steps to create a new application in beanstalk is -
1) Create a new application say "test app" in Elastic beanstalk, chose the region which best suits your requirement.
2) Create a new environment in the application "test app", select the application server you like to have i.e, tomcat 6 32/64 or tomcat732/64.
3) upload the .war in the newly created environment.
4) You can provide a custom Cname through which you can access you webapplication from browser.
5) Finally based on your requirements you can set the healthcheck status time interval, scaling unit
Got it... thanks for the detailed description.
You can make it in two ways
Create a singleBeanstalk application.
create different environments for each company within the created application, and in every environment deploy the .war file and provide the resources as per your requirement such as tomcat 6/7, minimum number of instances & maximum number of instances for Auto scaling. Health check monitor interval, no. of times to check before timeout etc.,. and finally assign the cname (i.e, the url by which you access the application) associated with the company name, like if the webapp is for xyz company then provide cname as xyz.elasticbeanstalk.com.
2 . Create multiple Beanstalk applications i.e., one for every company and in each application you can create multiple environments like Development, Beta, Staging and live - based on your requirement.
And coming to DB
Go for RDS if your DB is relational DB. Two ways to plan for multiple company's is
1) Create a single RDS and create multiple schema's in it i.e., one schema for one organization.
2) Create separate RDS for every organization - recommended if DB records are more
Let me know if you have any queries.
Happy to help...:)
please find me inline comments in bold.
Currently, the application is installed on a company's server, and users from the company that will use the application are created.
How is the installation done, and what is the architecture(x86/x64) and platform(windows
server/linux) of the server
The application knows how to manage its users. So every company that needs this application, buys a server and the application is deployed on the server.
Buys a server in the sense - you guys are providing the application and they are
launching in their server, i mean in their own infrastructure.
The facts i understood from your reply is, that you guys provide a web application to
different company's. And those company's deploy your webapplication in their
application server and DB in their DB server.
Correct me if am wrong