Hi Nerad,
To complement what Fulup posted, I can also point to the latest documentation we
have on widgets config:
https://docs.redpesk.bzh/docs/en/master/developer-guides/2.2-config.xml.html
Hope this helps!
---
Stephane Desneux - CTO - IoT.bzh
stephane.desneux@xxxxxxx - www.iot.bzh
On 16/07/2021 14:29, Fulup Ar Foll wrote:
Nerad,
Did you check following document ? It is a training on AGL-V3 security model
that we also gave two years ago. It is old but matches with the version used by
AGL: https://iot.bzh/en/publications/38-2019/101-lesson-ensta-2019
Also note that in past two years things moved significantly. While AGL choose to
freeze on application-framework V3, we announced the V4 just before last year
Christmas. V4 source code is now public and available from:
https://github.com/redpesk-core . The new V4 is obviously 100% backward
compatible with V3 bindings, but it introduces a lot new features as: SeLinux,
oAuth2/OpenID-connect, FlatBuffer, Object Lazy Synchronisation,
health-monitoring,... that are not yet supported by AGL. We also moved out of
widget package W3C model that is now obsolete since 2018 and use RPMs a default
application delivery model.
Fulup
On 12/07/2021 23:11, Nenad Milidrag via lists.automotivelinux.org wrote:
Hi everybody,
My name is Nenad Milidrag and I am working for the company that provides
Mobile Device Management (MDM) solutions. We are investigating if we can
provide MDM service for devices that are running AGL.
I have been reading about building the application for the AGL that can access
certain APIs. After a few days of research, I have exhausted most resources I
have found and still have very wage clue about API access control. I guess the
question is how Cynara gets configured? I am assuming that when one writes
the config.xml for the wgt package he will specify all required and optional
APIs. Then when the application is installed using afm-util, the installer
will be prompted with the question if access to the API should be allowed or
declined. Installers' feedback will then be saved into the Cynara
configuration. Is this correct?
Further, some documents are talking about signing the application and then
some are talking about different tiers of the users but more in the context of
proposals and without details on how it will be used. Is there a document
that provides details on these two topics?
I am apologizing for the long email.
Thank you for your insight.
Regards,
Nenad
[SOTI Taking Mobility to Endless Possibilities]
<https://soti.net/lp/soti-newsletters-sign-up?utm_source=Email&utm_medium=organic&utm_campaign=employee_signature&utm_content=newsletter_signup>
This e-mail is confidential and is intended solely for the use of the
addressee(s). Content is not to be relied upon by any person other than the
addressee(s), without prior written approval of SOTI. If you are not the
intended recipient, please notify us immediately, destroy any copies and
delete from your computer systems. If you have received this e-mail in error,
any use, disclosure, dissemination, forwarding, printing or copying is
strictly prohibited. Although this email and any attachments are believed to
be free of any virus or other defects which might affect any computer or IT
system into which they are received, no responsibility is accepted by SOTI for
any loss or damage arising in any way from the receipt or use therein.
--
/Fulup Ar Foll, CEO
Tel: +33.257.620.241 Mobile: +33.619.921.323
www.iot.bzh <http://iot.bzh> /
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#9316): https://lists.automotivelinux.org/g/agl-dev-community/message/9316
Mute This Topic: https://lists.automotivelinux.org/mt/84164629/2167316
Group Owner: agl-dev-community+owner@xxxxxxxxxxxxxxxxxxxxxxxxx
Unsubscribe: https://lists.automotivelinux.org/g/agl-dev-community/leave/4543822/2167316/883735764/xyzzy [list-automotive-discussions82@xxxxxxxxxxx]
-=-=-=-=-=-=-=-=-=-=-=-
