Connecting to DMA radius manager and Managing Data - radius

I have a DMA Radius Manager with admin account. My company wants to create a custom application that autheticate with the DMA Radius Manager and manage data without accessing the web pannel. I'm wondering if it's possible, if yes can you please show me where to start maybe a small tutorial ?
I don't know if the idea is clear, Thank you.

Related

How to Encrypt/decrypt data in a Waves Keeper Web App?

currently developing a new feature on my Web App i'm having a question:
I encrypted some data because i dont want it public in the blockchain but i have some concern about this, ideally the encrypt/decrypt password should be the privatekey of the keeper connected user but since we don't have access to this info in Waves Keeper, what would be the best practice ?
How can we encrypt/decrypt data in a decentralized manner with Waves Keeper?
im currently using a password predefined by me as an environment variable on the server side but this is far from ideal and definitelly centralized aside of having several downside.
Of course there is few backup options like:
1) Simply avoid put any non public data in the blockchain
2) Add an encrypt/decrypt field in the App requiring user to enter his password everytime
Both would work but are just getting around the problem and not ideal, would like to know if there is any good solution first :)
There are two methods in Waves Keeper API to encrypt/decrypt data. You can find details on the github.
https://github.com/wavesplatform/waveskeeper

Connecting a device to an account

So the title sounds stupid. I'm not really sure how to really word it, but I want someone to help guide me on what to look for. Little back story first so I'm working on a Raspberry Pi project that involves using an LTE service currently I have a dashboard running on a AWS EC2 web server with a simple user working user login.
I have a raspberry pi that is directly pointed to the dashboard/account via an IP address. I want to know how to do something like giving a device an ID and having it connect to an account. So for example with Nest products you have the QR code on the camera you take a photo and that devices get applied to your account.
Is this even possible with Raspberry Pi(I'm sure anything possible, but is it feasible? If so what should I look into or learn how to do such thing. I know its not something that can be answered in a short paragraph just looking for some guidance.
Right, thanks. Well, I think you need to program this into the pi server app. So currently your Pi is reading a sensor and sending this data to the web server, right? I suppose you have a daemon running, taking readings, and doing an API REST call to the server backend, correct? So what you want is to have a unique code for each pi, sent with the API call, and then on your DB server side,you store all readings related to their unique code.
You don't need to pre-validate this code, there are GUID generators that will create a number for you, guaranteed to be unique for all eternity, so on the PI, you set it up once, to create the PI's code, and use it from then on. Now, server side, then associating a device with a user is a matter of choosing the data associated with a given gui. And I think that covers it.
You can improve on this basic idea by giving it more thought, but I think it's a good starting point! Do let me know if I can help you with anything else!

How can I scale Botkit application

I new to botkit. Still exploring the framework.
How does the botkit scale? Can I set up multiple server and route request randomly? Will the context be preserved if each user requests end up in different server?
Saving the session into dbs is the only way to go ahead, Botkit does not support it by default.
There are other people trying to solve similar problem, this might help https://github.com/howdyai/botkit/issues/251

PJSIP via CLI on Raspberry

I am new to Raspberry and VOIP. I am interested to make a door intercom system using raspberry, as I read most of the post here and those are really helpful,one of the raspberry is acting as server (Asterisk and PBX). I was able to call using sflphonebut that was only for desktop mode and I am interested to call using CLI and for that I installed "PJSIP" as reffered by most of users, but don't have any idea what to do next (I mean how should i start). As it is written after installation I am supposed to try for "pjsua" and "pjsystest" in pjsip-apps/bin, but it doesn't ring any bell for me.
Sorry for my level as beginner but if you don't begin how are you supposed to masters it.
I shall be very thankful.
so i can't explain all of the stuff you need to know, but with this Site you should be able to register to you PBX. It's an documentation to the high level API of PJSUA. If you go further on that site they will lead you through the things you have to do to establish a call.
Although this can be very frustrating because there are many error that can appear. There are some python test application under pjproject/pjsip-apps/src/python/samples, here you should firstly try to establish a call between two clients to be sure you server is well configured.
Just for info, the dest_uri you have to give in the call.py is like so sip:ip:port and you have to change the values in the register.py to your client infos. Then run the register.py in one shell and the call.py in an other shell.
Hopefully i could help you over some barriers, feel free to ask if something was unclear.

CentOS FreeRadius and WPA 2 Enterprise

It is to my knowledge that as I finished setup my FreeRadius on my CentOS server, I point my router to the server and all is done.
Any user will need to use WPA2-Enterprise to login.
I previously used DAC to authenticate my user, after setting up RADIUS, do I no longer need a web page like how DAC need, right? The login form will be presented on the users device OS, right?
After thinking a lot, this is what I know.
DAC Authentication is controller-based, and as I used local database for authentication check, changing it to RADIUS will still require that webpage to be present.
In order to switch to WPA2-Enterprise, I need to configure each and every access point to use WPA2-Enterprise, and point them to the RADIUS server. That's mainly because I use Fat APs, if the access points I have in my environment are thin APs, they can simply fetch configuration from my controller.