I developed a window mobile phone 8.1 application and register that application to receive push notification under our company account, then i created a hub in windows azure account and copy that package id and secret id in that hub configuration section.
i created a channel using PushNotificationChannelManager then i registered the channel in hub in the application start up OnLaunched event. ( Windows phone 8.1 )
i created a notification hub client and pass the toast template variable in SendWindowsNativeNotificationAsync method. ( Console application )
You could perform NH registration only for registered users, so only registered users would receive notifications.
It is also possible to perform NH registration via backend (console application). Obviously, to do that your device application should get channel and then pass it to backend somehow (web services or similar). At this point you could enforce any authentication mechanisms, security checks, encryption or whatever you want before register channel in NH. The thing is only backend knows NH connection string, it is not exposed with client app and nobody else can create registration even using reverse engineering against device app.
Click configure tab on azure hub, and choose "Enable unauthenticated push notifications" and save, it works!
Related
I have created a web application as a private developer for a friends company. All the code lives within my personal Azure Dev Ops portal and at present has a pipeline configured to build and a release configured to release to a web application within my Azure tenant.
How can I now create a new release pipeline so that the code will be published to the a web application within the companies official Azure tenant?
We have created an Azure subscription and a web application using my friends company office 365 account but I somehow need to grant access or authorise my personal Azure Devops portal to publish.
After a lot of searching and playing it would seem there are many many ways to do this. In the end I went down the route of adding my friends work account to my Azure DevOps project so that they could create a service connection by authorising with their Office 365 account.
Once done I gained access to the subscription when creating the release.
We have several instance of APIM created a few months ago. Earlier this month we found a new developer portal. The new developer portal works fine for some of our APIM instance. However some of them have an internal VNET setup. So we configured custom domain for Gateway, New developer portal and Direct management. However, if I go the new developer portal it never loads correctly. It tries to access some endpoint of direct management and get request time out.
From the documentation:
If your API Management service is in an internal VNet, your developer
portal is only accessible from within the network. The management
endpoint's host name must resolve to the internal VIP of the service
from the machine you use to access the portal's administrative
interface. Make sure the management endpoint is registered in the DNS.
In case of misconfiguration, you will see an error: Unable to start the portal. See if settings are specified correctly in the configuration (...).
https://learn.microsoft.com/en-us/azure/api-management/api-management-howto-developer-portal#do-i-need-to-enable-additional-vnet-connectivity-for-the-new-managed-portal-dependencies
The only official resource available for authenticated push notification on windows phone 8 is http://msdn.microsoft.com/en-us/library/windows/apps/ff941099(v=vs.105).aspx but it doesn't meets the requirement. Can someone list the steps for authenticated push notifications on windows phone 8 using IBM Worklight 6.1.
Per the IBM Worklight user documentation:
To use an authenticated push notification service, you must first set
up a Secure Sockets Layer (SSL) certificate keystore. For more
information, see SSL certificate keystore setup. The keystore can
contain several certificates, one of which is the certificate for
authenticated push notifications to Microsoft Push Notification
Service (MPNS).
You must also authenticate your web service with Microsoft, as documented in the Windows Phone > Development Center at http://dev.windowsphone.com/en-us/develop/.
The serviceName attribute from the application descriptor is passed to
the application's client side, and is used when a new notification
channel is created. The URI token of the notification channel starts
with "https", rather than "http".
The keyAlias and keyAliasPassword
attributes are used by Worklight® Server to extract the certificate
from the Java™ keystore file, so that it can be used in the handshake
process with Microsoft Push Notification Service (MPNS). Any push
notifications submitted to the application will be authenticated and
secure.
The end result should look something like this:
<windowsPhone8>
<pushSender>
<authenticatedPush serviceName="myservice"
keyAlias="janedoe"
keyAliasPassword="a1b2c3d4"</authenticatedPush>
</pushSender>
...
</windowsPhone8>
There is nothing else to it.
If you are encountering issues, you should probably actually note those in the question body.
I want to develop a Windows 8.1 app that uses a client-server model to send some data from the server to multiple clients through Wifi or within a network.
the functionality is similar to what's in this app http://apps.microsoft.com/windows/en-gb/app/67786fc8-b27b-4ea1-92f5-1ad8abfbeda1
would you please guide me to the APIs or concepts to use to achieve such functionality ?
I am just wondering is it good idea to give NETWORK SERVICE permission for MSSQL database, can it open any security holes? Then I don't need to set any login parameters in my web app(ASP.NET MVC) config file, I go with integrated permission.
Looking at MSDN, Windows Network Service Account has minimum privileges in windows and it acts as the computer on the network.
But I personally believe that, if you are using it for personal development then it is ok to use network service to access database (if they are on same machine). You might need to configure application pool of your web app to use that service as well in order to have your web app authenticated by SQL Server.
But if it is for enterprise, then I would suggest you to create a separate domain account and use that domain account for both SQL Server and Web App. In that way you will have more better control over that account and it's permissions and less chances to find out that you have given more than required permissions to some default windows account.