When trying to import a newly generated JSS application into Sitecore, the jss deploy app --includeContent --includeDictionary returns the following error:
Unexpected response from import service:
Status message: Forbidden
Status: 403
Version info:
Sitecore version 10.02
JSS Version: 19.0
For jss setup, I specify the Sitecore instance as NOT accessible via a network share.
It may be issue due to JSS version, i also had jss deploy issue, details are: https://rinkusitecore.wordpress.com/2021/03/20/app-deploy-issueforeach-import-for-sitecore-jss-using-sitecore-9-3/
It seems for sitecore 10.0, need jss version 15, checkout: https://dev.sitecore.net/Downloads/Sitecore_JavaScript_Services.aspx
So try to create your app based on jss version 10 like jss create react -b release/15.0.0
But In your title you mentioned sitecore 10.2, in that case JSS version is correct (https://dev.sitecore.net/Downloads/~/link.aspx?_id=B5D60A30ADD1495C9B011E793AF6884F&_z=z)
So confirm it first.
Related
When trying to import a newly generated JSS application into Sitecore, the jss deploy items command returns the following error:
Unexpected response from import service:
Status message: Bad Request
Status: 400
Version info: Sitecore version 10.02 JSS Version: 19.0
I used the --branch release/19.0.0 parameter when creating the JSS application to ensure the correct framework version.
Sitecore is running on another server on the network.
I've created a file share on the Sitecore server and specified it for jss setup which otherwise warns that jss deploy config, jss deploy files, and jss deploy app cannot be used with remote Sitecore.
When I first received the 400 error, the server admin added the IIS app pool user to the "Performance Monitor Users" & "Performance Log Users" groups per This Stackoverflow question, but this didn't help.
When running the JSS command, I'm logged in with my corporate network (Windows) ID on my local PC. In Sitecore, there is are Sitecore Admin and test user accounts. Does my corporate network account need to be mapped to a Sitecore account?
I resolved this error when I discovered that I was using an incorrect entry for the Sitecore hostname. When I corrected it so that it mapped to the path to the Sitecore folder, I no longer receive the 400 error.
Description:
I build the APIM from this commit and deploy the product on the VMs.
I configured APIM using Documents 1 and 2
Then start the traffic-manager, key-manager, and publisher without any error.
But when I tried to log in to example.com/publisher, I experienced some errors.
Like below:
logs.txt
After getting these errors, I checked the service providers section and saw that the apim_publisher application was created but OAuth keys didn't exist.
Then I checked the consumer_key and consumer_secret's value on the AM_SYSTEM_APPS table in apim_db database, and both of them was undefined
Steps to reproduce:
Build product-apim from this commit
Move wso2am-3.2.0-SNAPSHOT to 5 VMs.
Run the below command for profile optimization for each node.
sh bin/profileSetup.sh -Dprofile=$PROFILE_NAME
Run components in the following order:
sh wso2am-3.2.0-tm/bin/wso2server.sh -Dprofile=traffic-manager
sh wso2am-3.2.0-km/bin/wso2server.sh -Dprofile=api-key-manager
sh wso2am-3.2.0-pub/bin/wso2server.sh -Dprofile=api-publisher
Open the publisher page
Affected Product Version:
APIM 3.2.0 (MariaDB)
Environment details (with versions):
OS: Ubuntu 18.04
Client: Ubuntu 20.04
After installing version 3.0.0 of the WSO2 API Manager I am getting errors trying to access the Publisher and the Store.
This is the error at the Store (https://myhost.my.org:9443/store)
Error 405 - Method Not Allowed
As for the Publisher, the url https://myhost.my.org:9443/publisher redirect to this url...
https://myhost.my.org:9443/authenticationendpoint/oauth2_error.do?oauthErrorCode=invalid_callback&oauthErrorMsg=Registered+callback+does+not+match+with+the+provided+url
...and displays this error message:
invalid_callback - Registered callback does not match with the provided url
Notes:
I can access the admin page just fine (https://myhost.my.org:9443/carbon)
I replaced every occurance of 'localhost' with 'myhost.my.org' in every file in .../wso2/wso2am/3.0.0/repository/conf, including 'carbon.xml'
Logs reveal the following: (.../wso2/wso2am/3.0.0/repository/logs/wso2carbon.log)
WARN {org.wso2.carbon.identity.oauth2.OAuth2Service} Provided Callback URL does not match with the provided one.
Stack:
Ubuntu 18.04
OpenJDK 11.0.4
WSO2 API Manager 3.0
Installation steps followed:
https://apim.docs.wso2.com/en/latest/GettingStarted/quick-start-guide/
Installation commands:
sudo apt install openjdk-11-jre-headless
java -version
openjdk version "11.0.4" 2019-07-16
OpenJDK Runtime Environment (build 11.0.4+11-post-Ubuntu-1ubuntu218.04.3)
OpenJDK 64-Bit Server VM (build 11.0.4+11-post-Ubuntu-1ubuntu218.04.3, mixed mode, sharing)
sudo wget https://product-dist.wso2.com/downloads/api-manager/3.0.0/downloader/wso2am-linux-installer-x64-3.0.0.deb
sudo apt install ./wso2am-linux-installer-x64-3.0.0.deb
sudo service wso2am-3.0.0 start
The installation notes refer to localhost/127.0.0.1. But I am installing on myhost.my.org.
Files manually modified in .../wso2/wso2am/3.0.0/repository/conf (replaced 'localhost' with 'myhost.my.org' and '127.0.0.1' with 'this.is.my.ip'):
api-manager.xml
broker.xml
carbon.xml
datasources.properties
deployment.toml
event-broker.xml
log4j2.properties
messaging-event-broker.xml
metrics.xml
registry.xml
thrift-authentication.xml
Any ideas? Thanks!
You have to update the callback URL in the Service Provider.
1) Go to /carbon and edit the relevant SP.
2) Edit the OAuth app in it.
You will see the callback URL like this.
regexp=(https://localhost:9443/publisher/services/auth/callback/login|https://localhost:9443/publisher/services/auth/callback/logout)
Update all occurrences of localhost with your hostname.
Save both OAuth app and SP.
About:
his is the error at the Store (https://myhost.my.org:9443/store)
Maybe you can find what you need at https://myhost.my.org:9443/devportal
If you encounter the same error with callback URL on devportal, log into Management Console, under list of Service Providers, edit admin_admin_store instead.
I am currently working on deploying Apache Airflow 1.10.0 to a Kubernetes cluster. I am running into some dependency issues with Flask.
If I use the current version of flask-login (0.4.1), I receive this error:
apache-airflow 1.10.0 has requirement flask-login==0.2.11, but you'll have flask-login 0.4.1 which is incompatible.
With this error, the UI won’t render, and instead, I see a text bomb followed by many flask-appbuilder/flask-login warnings.
If I use the Airflow’s requirement of flask-login (0.2.11), I receive this error:
flask-appbuilder 1.12.0 has requirement Flask-Login<0.5,>=0.3, but you'll have flask-login 0.2.11 which is incompatible.
With this error, the UI renders with Airflow 1.9 features and CeleryExecutor won’t work.
This was fixed with an Airflow update: https://github.com/apache/airflow/blob/master/UPDATING.md
I am trying to use Django Facebook to register users in my app.
Right now I am in local develoment and after giving persmissions to the app in Facebook and following all indications in readthedocs, I get the next error:
Please specify a Facebook app id and ensure the context processor is enabled
Django version: 1.8
Python version: 3.8
This was an error django-facebook code, which has been fixed. Make sure you are using django-facebook 6.0.4 or later. Even if the latest model is not yet shipped you can get it by doing pip install git+git://github.com/tschellenbach/Django-facebook.git