I want to install System Service application, But In WSO2 documentation, It has written that I need to sign the application via Device Firmware Signing key.
What is the meaning of this line [Device Firmware Signing key] and also how to get the System application signed by Device Vendor?
Can't Understand how to install this System Service Application.
Related
I'm trying to build an application with a WSO2 Application server and Identity server.
the soap server which is based on Axis2 Framework needs to have WS-Trust based Authentication. For learning, I'm following this blog http://www.vitharana.org/2015/01/how-ws-trust-sts-works-in-wso2-identity.html
At the 14th steps, I have to click on security but In latest WSO2 Application server I'm not able to find how to enable the Security feature.
I'm using 5.3.0 Version of Application Server
As you can see there is no link on Unsecured for HelloWorld Service.
I'm I missing anything?
All the WSO2 products based on carbon kernel 4.4.x doesn't contain QoS features. WSO2 AS 5.3.0 is based on kernel version 4.4.x and therefore it is not supported. You can use WSO2 Developer Studio in order to apply QoS features
I want to setup all my devices as COPE. WSO2 EMM setup is complete and working fine. Only thing is left is to sign the system service application with the firmware key. I am using Google devices only (Android one, Motorola G2). From where I can find the key and password to sign the application.
Is there any other alternative way to get the application signed?
As per documentation, "Sign the application via the device firmware signing key. If you don’t have access to the firmware signing key, you have to get the system application signed via your device vendor."
But I am not able to find the device firmware signing key.
Any guidance will be really helpful.
There are couple of COPE enrollment types WSO2 IoT server supports,
1. Device owner mode
2. Kioski mode
3. System application
The first 2 options can be used with any out of the box Android device. However system app is targetted towards original equipment manufacturers(OEM) who builds Android devices and maintain their own Android versions. This mean they maintain a version of Android OS image and does the installation to some customer device. If you are an OEM, you should have these keys with you. If you are not an OEM and still needs to use out of the box devices such as Motorola or Samsung to install system app, you need to form a partnerships with those vendors to get the sign the system service app. Unless you need to perform operations such as reboot or firmware upgrade. You do not need systrm service app. In that case i would recommend you to go for option 1 or 2. What are the features that you are looking at? Also it is best to seek wso2 professinal services if thats an option for you https://wso2.com/contact/
I have setup WSO 2 emm 2.0.1 in development environment. I was able to successfully enroll android device and check the MDM policies of android device. I did not do any additional platform configuration by creating any kind of certificate to get android emm working. But in case of IOS wso2 profile is not getting installed. And while installing iOS agent error is can not connect serverIP. Do I need to create all the certificate as mentioned in the link https://docs.wso2.com/display/EMM201/iOS+Platform+Configurations . I have never worked with android and iOS devices previously .
Please help !!
Yes you need to follow all the instructions provided in the following documentation in order to enable communication with your ios devices.
These are protocols provided by Apple to ensure the device security.
https://docs.wso2.com/display/EMM201/iOS+Platform+Configurations
https://docs.wso2.com/display/EMM201/Generating+a+MDM+APNS+Certificate
Make sure to complete all the configurations where you need to put your ip or domain as provided in the documentations
Obtaining a signed CSR from wso2 also required in order to use emm server to manage ios devices.
Refer to the below tutorial if you are using a public server with a SSL certificate obtain from a know Certificate Authority.
http://kamidupunchihewa.blogspot.com/2016/07/configure-device-communication-when.html
I am facing problems while connecting with the emm store from my device.
I want to know what changes I have to make so that I can access emm store and can download the apps on my device. Any help will really be appreciated. I am not able to understand this
You do not have to perform any android configurations for the emm server in order to enroll android devices. EMM server contains configurations for android.
In the documentation you are provided with instructions how to modify
the agent app to use https protocol rather than http protocol and
generate a new .apk file.
In order to connect your login to store and install applications to your device you need to provide related permissions to the related user. Use the carbon console for grant permissions
I would like to deploy an Application using XenApp on a linux server. Is it possible to do this via virtual box on a remote linux machine?
So far I have installed virtual box on a centos based linux machine.
I installed a Windows 2008 R2 Server virtual machine.
I then tried to install XenApp on the windows 2008 server.
After updating the windows 2008 server with the latest stuff and adding .net 3.5 and sql server express I got XenApp installed.
I am stuck at the point of deploying the Single Sign-On service. It wants a "UNC path to the central store of the citricl signle sign on". Does anyone know how to set that up?
I don't have a domain controller, nor do I have active directory installed. Do I need those things? I was really hoping to avoid that.
What does XenApp require? I kind of figured it would be plug and play but it doesn't appear that way and the installation instructions are very vague about system requirements.
Thanks
Single Sign-On is not required for XenApp.
From the documentation
Citrix Single Sign-on (formerly Citrix Password Manager) provides password security and single sign-on access to Windows, Web, and terminal emulator applications running in the Citrix environment as well as applications running on the desktop. Users authenticate once and Single Sign-on does the rest, automatically logging on to password-protected information systems, enforcing password policies, monitoring all password-related events, and even automating user tasks, including password changes.
Basically: SSO needs a place to put the Central Password Store.
Just give it a path to a network share that all XenApp servers can access. If you're using a single machine; create a local network share and point to it using UNC
\\localhost\SSO_Store