I have built a Kaa server from the source code using the guide at the following link. After which, I followed the guide at the following link to install the Kaa node service.
I am deploying the build on Ubuntu 16.04 and using MariaDB and MongoDB as the SQL and NoSQL databases respectively. I followed every step from both the guides and the server starts successfully.
I am able to navigate to the Kaa admin page using the link http://YOUR_SERVER_HOST:8080/kaaAdmin, and have created an admin user as well.
However, when I log in, I don't see all the panels. I only see the following panels.
I don't see the user, tenant or the application management panels. The tenant section only allows me to add a new tenant where I can only enter the tenant name and nothing else.
Is there additional step to be performed to enable the other panels? I am not sure what I am missing.
Any help is appreciated.
Related
I have problem with node-red.
I have a server and i have node-red running on it, i know how to create user authentification by editing setting.js file but what i want to do is that i want to be able to create other users from a webpage that is running on the same server.
I can run a python script that edit the setting.js file and i can edit it mannualy,
but i want to be able to create and remove users from the webpage that is running on the same server.
i am using ubuntu and ngninx on my server.
The Node-RED security documentation includes a section on adding custom user authentication here. It explains how you can replace the hard coded user information with a module that will authenticate a given user. Editing the settings.js is probably not the right approach, especially as it will require you to restart Node-RED after each change.
With this approach you can build your own back end to store and manage users. There are a couple of examples of such code available, including this one that I have written that uses MongoDB to hold the user information. The management app that creates users can be found here, but you can write your own in Python if you want.
Just as a reminder, Node-RED is not a true multi-user environment, even if you declare a number of users, they will all only have shared access to one instance and set of flows. If you want a truly multi-tenant (each user has their own instance and flows) deployment you should probably look at the entire series of posts in that collection that explains how to build such a system. You can start here.
I have been working with Kyle H. in Azure Support Chat and he recommended that I post this here.
Please be understanding, as I have read every related Stack Overflow post relevant and have exercised due diligence.
I have completely deleted and restarted both my Azure resources AND source code multiple times. Using this guide: https://learn.microsoft.com/en-us/azure/bot-service/bot-builder-howto-deploy-azure?view=azure-bot-service-4.0
The bot project is using the v4 template 'Echo'.
In Azure Portal, Test in Web Chat: "There was an error sending this message to your bot: HTTP status code Forbidden"
In Bot Emulator with ngrok configured: Cannot post activity. Unauthorized.
Following instructions here: https://learn.microsoft.com/en-us/azure/bot-service/bot-service-troubleshoot-authentication-problems?view=azure-bot-service-4.0#step-2
I ran: curl -k -X POST https://login.microsoftonline.com/botframework.com/oauth2/v2.0/token -d "grant_type=client_credentials&client_id=b7404e9f-0e74-4174-aa4f-447fdd96d7f0&client_secret=REMOVED&scope=https%3A%2F%2Fapi.botframework.com%2F.default" and I am returned a valid access token.
I have confirmed multiple times that my app registration is using https, as well as the /api/messages route, and that my app service has the two keys MicrosoftAppId and MicrosoftAppPassword and they are set appropriately. Including stopping and starting and the restart functionality. I have also ensured that during deployment(VS 2017 Publish), it removes existing files.
My last attempt was to upgrade the template 'Echo' bot to .net core 2.2 - which deployed successfully. I again verified app id and app password set as described above, and unfortunately both the Bot Emulator and Test in Web Chat failed with the same errors.
Edit 1:
I used 'Create new resource' and picked the 'Web App Bot' template. I chose the 'Echo' bot. I chose 'Automatically Generate Application ID and Password' as well. This resulted in a bot deployment that did not have authorization errors. However, I noticed that instead of a 'Bot Channel Registration' resource - it instead created a 'Web App Bot'. When inspecting 'Application Settings', application ID and password aren't present, yet it functions just fine.
Edit 2:
I researched deeper, and learned that the 'Web App Bot' created in azure uses the botFilePath and botFileSecret application settings and likely keeps the app id and app password there.
Edit 3:
There is a huge difference between the v4 BotBuilder EchoBot template you use in visual studio when creating a new project and the EchoBot template used in Azure when creating a new resource. Narrowing it down now.
Edit 4:
I was able to use the Azure created web bot and modify it to continue my work. Was not possible with the Vsix templates even with ensuring app config and .bot file config were correct.
Edit 5:
I also learned that v4 doesn't support Microsoft Teams - and that was the entire purpose of my endeavor. v3 documentation is near nonexistent. So I think I'll be using an entirely different framework to integrate with Teams. I even attempted to implement: https://github.com/OfficeDev/BotBuilder-MicrosoftTeams-dotnet but my bot only responds with "Sorry, there was a problem encountered with your request" in Teams.
Edit 6:
I managed to get my bot functioning with Microsoft Teams, during the process solving the unauthorized error.
I created the Echo bot in Azure - and used App Studio in Microsoft Teams to add a manifest and add the bot to our team.
After that, I imported the project located here: https://github.com/OfficeDev/BotBuilder-MicrosoftTeams-dotnet/tree/master/CSharp/Samples/Microsoft.Bot.Builder.Teams.TeamEchoBot
Then I modified setup.cs to work with the encrypted .bot file, based on the source code that created the Echo Bot in Azure.
The VSIX templates are going to generate Startup code that uses the .bot file for appId/secret and, when deployed to Azure, is going to be looking for an endpoint named "production" which you would have had to add yourself to the default .bot file with the appid and secret from your provisioned bot.
For more details, check out this previous answer I gave on this topic .
If you are struggling to deploy your bot, I would recommend looking at this guide. The steps will walk you through creating a bot on Azure, and then you can download the source code, develop your bot, and redeploy it.
Glad I could help!
I started working with Sulu, and tried to implement the optional ArticleBundle. I used this documentation and composer installed elasticsearch 5.0.6 along with the bundle. All configuration files have been configured like the documentation, and while the server is starting, there is still no "Article" options like in the Sulu demo (you can log in with admin / admin and check it out).
I also encountered the error No alive nodes in your cluster while performing the last commands that are related to ElasticSearch. What Am I missing?
Have you seen that the SuluArticleBundle has a dependency to elasticsearch (which is a third party application). This has to be started before running sulu with the article-bundle. Additionally you have to add the security-context to the user-role. Open the User Role of your user and simply add it.
I am running kaa 0.10.0 on ubuntu 14. Since the outgoing email was not properly configured, I created many tenant admins. Is there a way to delete them?
I do not see the delete button as the doc http://docs.kaaproject.org/display/KAA/Administration+UI+guide
shows.
Thanks for help.
James
Looks like there is no option for the Kaa 0.10.0 release to delete a tenant admin. The documentation you referenced is for Kaa 0.9.0 (and prior) only. The Kaa 0.10.0 documenation is available here.
Also, please note the user types defined in Kaa. For example, to add, modify (or delete if that option is available) a tenant admin, you should sign in as Kaa administrator.
james800,
I suppose what you're referring to is "deleting tenant" instead of "deleting tenant admin"? If you're referring to deleting tenant admin, you can have a delete button after clicking on one of the tenant.
I'm trying to use the boxr package to link my box account to R-Server.
I get as far in the box_auth() instructions as step 3 from the box pdf https://cran.r-project.org/web/packages/boxr/boxr.pdf
A window pops up and I authorise connection then I get the error 'Safari can't connect to the server'.
I have no knowledge of how apache or web development works so forgive my naivety, I've come to understand the problem is I don't have localhost set up on my Mac.
I'm unable to turn these features on because it requires admin rights and my company won't allow users to have this.
Is there something else I can put in the redirect_uri box apart from localhost that will allow this to authenticate?
Thanks
The issue i had was mostly that authenticating box through R-Server isn't supported. https://github.com/brendan-r/boxr/issues/23
To get around this I used my personal laptop to authenticate locally then uploaded the .Renviron and .boxr-oauth files to R server (which is the advice in the github post)
This was slightly tricky as R wasn't showing the .boxr-oauth file but I managed to copy it to a folder, zip the folder, then upload that to R-Server.
Now running the box_auth() function authenticates as it should.
As of v0.3.5 (November 2019) boxr has a new alternative authentication method designed for remote servers, box_auth_service(), that closes issue 23. It's slightly is different than the oAuth way, because it uses "Service" accounts as the actors instead of the "User" account. But the "Service" accounts are what's needed to maintain security within a organization, so we opted for that. Please open an issue on the repo if you run into any issues.