I have a question regarding the distribution of apps through the IBM mobilefirst app centre.
The mobile client would need to have an apple certificate as it will be place on the store so that users can get access to the application centre via the mobile client
However, do the apps within the application centre also need to be certified by apple?
Can anyone help confirm this? or share some insight
There are no apps inside the appcenter application. They all reside on a remote server and they never go through Apple.
Related
Basically how do I initialize the flow so a use can login to their desktop from their mobile phone?
Any help or advice in pointing to their docs for the right flow. https://developer.transmitsecurity.com/sdk-ref/webauthn/interfaces/webauthnsdk/
I'm trying to implement a smooth authentication flow for an hololens 2 app in a no-internet environment. Following setup is running currently
I'm hosting an identity server (Ory Kratos) with OAuth2 possibilities that holds user information.
I'm hosting a resource API that only logged in users should be able to access.
The user should be able to access their resources within the HL app. Possibilities to solve this are
Redirecting the user to a 2D page like in this article. But typing a long password in an Augmented Reality app is hard.
Using a second device (smartphone/laptop) like in this blog. But requiring another device is suboptimal.
Both approaches are fine, but they both lack a smooth user experience. My idea was to utilize the Windows Accounts that are already on the HL device. Microsoft Docs has a small section on how to take advantage of linked identities on HoloLens, see here. But it doesn't really explain how to "link" them to a custom identity server.
So I was wondering, is it possible to use these Windows Accounts that are already on the HL device and somehow link them to my identity server?
Or does anybody have a better idea to provide a smooth authentication flow in Augmented Reality? I'm open for ideas.
Windows Hello may meet your requirement. It works with the Azure Active Directory account or Microsoft Account connected in Windows settings, and it replaces passwords with strong 2FA by verifying your biometric. Besides, in Windows Hello architecture you no longer need to host your Ory Kratos OAuth2 server.
I am currently using Azure Notification Hub to send push notifications. I however also need to make use of in-app messaging, a feature I am only of being provided by Firebase at the moment: Firebase In-App Messaging
Does Azure/Microsoft have such a service?
Newest
I found that when I clicked on the Azure Mobile Engagement link, the page jumped to the Visual Studio App Center page.
So I searched for relevant information and hope it will be useful to you.
Configuring App Center for Push Notifications
PRIVIOUS
Microsoft has Azure Mobile Engagement.
Azure Mobile Engagement is now generally available. Azure Mobile Engagement has SDKs available for Apple iOS, Google Android, Windows Universal Apps, Windows Phone Apps and Apache Cordova.
General Availability: Azure Mobile Engagement
We are using MobileFirst 7.1.0.0-MFPF-IF201705051403 version.
We found some fraudulent activity with one of our users using Mobile App.
How do I block this user/devices from further accessing our mobile first servers?
You can use the mobile application management feature to control user/device access. See here for more details.
I've been looking everywhere for an answer to this, it says it goes something like server > GCM > client, the client must register and then it sends the registration token back to the server, but the 'client' part im confused about, does this only work on applications on the device? or can the app be on a website too? so for example if my app is a website, can I have the registration process on a website instead of an actual app on the device?
Yes, the currently listed client apps are Chrome, Android and iOS. Fortunately, you can use Progressive Web Apps to handle push notifications to websites.
The usual prerequisites are listed there, such as creating the Google Developer Console project, and other PWA fundamental configurations (add, register, and install Service Workers). The succeeding steps are PWA-specific implementations for you to have push notification implemented on the web page.
Happy coding!