Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Issue] The supplied authentication is not authorized to access 'whisk.system/messaging'. #302

Open
patpatpat123 opened this issue Oct 24, 2018 · 2 comments

Comments

@patpatpat123
Copy link

Hello,

I might be facing an issue and I will be grateful for your expertise.
After building this project, I am not seeing 'whisk.system/messaging'.
I had a look at the documentation on packages: https://github.com/apache/incubator-openwhisk/blob/master/docs/packages.md But yet, no success.

Hence the step of creating the Kafka package wsk -i package bind /whisk.system/messaging myMessageHub -p kafka_brokers_sasl "["localhost:9092"]"
error: Binding creation failed: The supplied authentication is not authorized to access 'whisk.system/messaging' always fail.

May I kindly ask for some advice?
Thank you

@patpatpat123
Copy link
Author

Hello,

To follow up, I am currently facing this issue:
wsk -i trigger create MyKafkaTrigger -f /whisk.system/messaging/kafkaFeed -p brokers "["localhost:9092"]" -p topic mytopic -p isJSONData true
ok: deleted trigger MyKafkaTrigger
error: Unable to create trigger 'MyKafkaTrigger': Unable to configure feed '/whisk.system/messaging/kafkaFeed': The requested resource does not exist. (code ALQiXMmsge9APwcDYqdyt2epITdFh2yP)

Hence, I went to check about this kafkaFeed, and rightfully said, it is not here:
~/incubator-openwhisk-devtools/docker-compose$ wsk -i package get --summary /whisk.system/messaging
package /whisk.system/messaging: Returns a result based on parameters bluemixServiceName, endpoint, isBinaryKey, isBinaryValue, isJSONData, kafka_admin_url, kafka_brokers_sasl, password, topic and user
(parameters: *bluemixServiceName, *endpoint, isBinaryKey, isBinaryValue, isJSONData, kafka_admin_url, kafka_brokers_sasl, password, topic, user)
action /whisk.system/messaging/messageHubProduce: Deprecated - Produce a message to Message Hub
(parameters: base64DecodeKey, base64DecodeValue, kafka_brokers_sasl, key, password, topic, user, value)
feed /whisk.system/messaging/messageHubFeed: Feed to list to Message Hub messages
(parameters: endpoint, isBinaryKey, isBinaryValue, isJSONData, kafka_admin_url, kafka_brokers_sasl, password, topic, user)

The guide did not mentioned anything about creating this "kafkaFeed". May I ask in which step this is done please?

Thank you

@jmtoball
Copy link

I was facing a similar issue.
What does wsk -i package list produce for you?
After successfully running the installKafka.sh-script, you should have something like this:

packages
/whisk.system/messagingWeb                                             private
/whisk.system/messaging                                                shared
[…]

For me the issue was that the auth-key I first ran the script with was actually a guest-one, while you need the system one to install the packages into /whisk.system, so I ended up with

packages
/guest/messagingWeb                                             private
/guest/messaging                                                shared
[…]

which results in the "resource does not exist"-error when trying to create the trigger.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants