netsuite SDF error when deploy on WebStorm - webstorm

SDF Features are enabled.
On webstorm, I can validate (netsuite ide function) and it works.
When I try to the project, even if it's empty or not, the LOG returns:
The remote server returned an error:
https://system.na2.netsuite.com:443/app/suiteapp/devframework/ideinstallhandler.nl - Moved Temporarily

I solved this error by Adding the SuiteApp Deployment permission to the SDF Role attached to my account.
Please follow the guide on how to create the SDF Role in this document.
https://docs.oracle.com/cloud/latest/netsuitecs_gs/NSCDF/NSCDF.pdf - PAGE 7

I got this error with Eclipse after our account was upgraded to 2018.2 and I stopped logging in as Administrator.
This seems to be a permissions problem; I fixed it by creating an SDF Developer role with the permissions listed in that SuiteAnswers article, and then logging into the role using a token, following the links in the note on step 5. (You may not need to use the token; I didn't try it the other way.)

Related

WSO2 Identity Server - Get Role's Permissions

refer to this link we integrated CustomPermissionClaimHandler to our server without any errors but still we can't get the permissions of the users... I know how to create custom claims refer to this link and if I follow these 2 links' steps, I can create permission field like a textbox as shown on picture (testClaim and organizationID are examples about that from picture)... I thought that after integrating CustomPermissionClaimHandler I would see permissions like Role field as shown on picture with blue line but still it comes with empty textbox as shown on picture with green line. Is there any way to get the permissions?
EDIT: I can get JWT including my custom claims and if I decode it I see like this (as you see it doesn't contain permissions):
By looking at the JWT response, I can say you have done either or both of the following.
It seems there is a mistake in the guide of configuring the application-authentication extension.
If you have added,
[authentication.framework.extensions]
claim_handler="com.wso2.sample.claim.handler.CustomClaimHandler"
in to the deployment.toml, but you use the jar by building the code, there is a mismatch in the package name. You have to use the following config.
[authentication.framework.extensions]
claim_handler="org.wso2.custom.claim.PermissionClaimHandler"
Because of this configuration issue, your custom handler may not get executed even though that service got activated properly.
If the claim handler is active and the configuration is correct as step one, you might have missed something when mapping the custom claim to an oidc claim / adding it as an OIDC sope / configuring service provider claims

Google Cloud doesn't allow me to create my first project with admin role

I'm trying to create my first project in google cloud with organization's administrator account. I have access to the administrator's email and passwords and I am logging in with that account to do so. The problem is that when I click on create new project I receive the following error:
There was an error while loading /home/dashboard?project=proven-now-305315&authuser=1.
You are missing at least one of the following required permissions:
Project
resourcemanager.projects.get
Check that the project ID is valid and you have permissions to access it. Learn more
Send feedback
The detail is that in my resource administration panel I already gave the permission that they ask me to the resource as shown in the following image:
As I have read, the project IAM Admin role should grant the resourcemanager.projects.get role and as you can see in the image the resource rcv # .. which is the administrator has it activated, however I keep trying to create a new project and it doesn't allow me to do it. Any idea?
In case anybody else, like me, reaches this answer, I want to point out that the accepted answer is correct, but for me I had to also make sure that within the settings, I ensured that Project Creation Settings on the right pane and under the section of Cloud Resource Manager Api Settings was set to on. It was turned off by default. Many people on my team overlooked this as it is significantly smaller text.
This may be an option that was not present before or it was turned on by default in the past. For us, it was turned off.
Please refer to the included image for a visual representation of the
settings that need to be turned on.
The problem was for some reason the Google Cloud was disable for all users, I solved following this instructions. Solved with this!
To activate this service, please follow the steps:
Access the admin console and go to Apps -> Additional Google Services
Look for the service “Google Cloud Platform” and click on the box next to it
In to top right corner click in “ON”
Confirm you want to turn it on in the pop-up box.

Access Denied: Project PROJ: The user X#gmail.com does not have permission in project- pycharm use wrong email

I have this strange issue.
I have a private google account X#gmail.com with some projects on google cloud
and recently got a new email with accessibility to my workplace projects (also on google cloud) .
y#work.com.
working with Pycharm, I am required to tap into the company's projects and work with bigquery resources, yet I receive this error:
HttpError: https://www.googleapis.com/bigquery/v2/projects/proj/queries?alt=json
returned Access Denied: Project proj: The user X#gmail.com does not
have bigquery.jobs.create permission in project proj.> INFO
yyyy-mm-dd module.py:861] ...
clearly, Pycharm uses the wrong email- X#gmail.com.
so I went back to the:
google-cloud-sdk/bin/gcloud init
and changed my email to the correct Email- y#work.com. and chose the right project.
regardless, Pycharm is still insisting on using the bad email and I have no clue how to fix it.
any help would be awesome.
Try to create new authentication file using instructions on
https://cloud.google.com/docs/authentication/getting-started
then change GOOGLE_APPLICATION_CREDENTIALS to point to that file.
You can switch between personal and work accounts by switching GOOGLE_APPLICATION_CREDENTIALS variable.

IIS AppPool user permissions not working

I'm moving a PHP app from IIS7 to IIS8.5 on Win2012 R2. The app runs in its own application pool (MyPortal) and needs write permission on a sub-folder to create PDFs. So I assign Modify or Full Control permissions to IIS AppPool\MyPortal on the local machine, however the app is still unable to write to the folder. The only way I have found to allow it to do so is by giving Modify access to the local USERS group, which I'd rather not do (although I have no choice ATM).
The php-cgi.exe process is running under the MyPortal identity, but somehow isn't picking up the permissions I have assigned to the MyPortal user on the folder. The PHP process is doing a simple fopen command $file = fopen($tmp_filename,"w");.
I saw this similar post https://serverfault.com/questions/570033/iis-iusrs-and-defaultapppool-permissions-do-not-work which suggested it may be a permissions caching issue, solved by a reboot, but that's not worked in this instance.
Any suggestions as to what's wrong?
You've got it #Jan Reinlink. Anonymous Authentication needed setting to 'Application identity pool'. I had assumed that because the PHP process was running as MyPortal it was using the same permissions.

Error when posting achievements with user messages

When posting an achievement with a user message it gives the following error:
{"error":{"message":"(#100) You haven't enabled User Messages for this action type (127701393971353) yet. Please update your Open Graph settings in the App Dashboard","type":"OAuthException","code":100}}
No clue where to enable that.
Managed to get access to the setting by modifying the url manually with the id.
https://developers.facebook.com/apps/your_app_id_here/opengraph/action_type/127701393971353/
In case this helps someone else, I had this issue. My situation was: I had a live app with an approved Open Graph action. I needed to release a new version of the app but I needed a new Open Graph action for this so the earlier version still worked until users upgraded to the new version. When I used the new Open Graph action, I got this error. My problem was that I had made a simple typo error in the bundle id of the new app version so it didn't match with the bundle id I had specified for the iOS settings in the Basic Settings page in the Facebook Developer app. The clue was that in the error given in the Xcode debug console, the app id didn't match up.