There are plenty of examples for Windows Desktop apps that will say whether or not the current user is an Admin.
Here are two
http://code.msdn.microsoft.com/windowsdesktop/CSUACSelfElevation-644673d3
http://msdn.microsoft.com/en-us/library/86wd8zba(v=vs.110).aspx
My problem is that I need to check within a Windows 8 Store App and they have a subset of the main .NET api. The stuff around Principals and Role are missing.
The Windows.System.UserProfile.UserInformation class looked promising but that was a dead end.
Can it be done?
Thanks
This is useless, because Store Apps don't run when you have an account with full admin rights.
The Sandbox around the Apps requires UAC/ filtered rights. So your apps get never full admin rights and you can skip this check.
Related
I'm considering implementing and publishing a Web App using Google Apps Scripts, which I'm quite familiar with for personal projects. I've never published a project to share with other people but I have an idea that would fit perfectly well for consumer users, probably for thousands of them. I've googled for the last 24hrs to see if there's any experience with simultaneous executions of a Web App when it runs as "user accessing the app" but I've failed to find any direct answer to my questions.
According to Google Developers Documentation, there is a daily limit of 30 simultaneous executions of the Web App, which coincides with the results of this test. However, neither the documentation explains on what conditions that limit would be reached nor the test was run with different users accessing the Web App authenticated.
Before trying to test it myself, which I find hard to do since right now I have no access to more than 30 different Google consumer accounts, I'd like to ask if there is someone who has direct experience publishing Web Apps using GAS with permissions set as "user accessing the app" and has found errors beyond the 30 simultaneous users.
Thank you.
Edited: 14/jul
I need help with publishing an app me and my team developed. It currently is in beta phase and we need testers. We thought of publishing it in the store as an open free beta app and ask for people to download it and report their bugs. After all the testing bugs are fixed the app will go public as v1.0 but not as free. We do however want the people who originally downloaded it to get all the updates for free as a reward for their help of testing our help and never have to pay for the app. How can that be done?
As you probably know Beta App is different than 'Normal' App - so after finished test you need to publish new application (you can't change beta to normal).
What you are asking is called targeted distribution - you can hide App (you will need to submit one more App for that purpose) from users browsing the store, and send a link to those who you choose (Beta testers). But you cannot prevent such a situation when a beta tester send this link to other person. So you have to cosider it.
EDIT
You cannot do such a thing like in beta version - create a list of user that will be able to use it.
The other solution that comes to my mind - you can create 'Beta' App that is the same as Normal App and alow specific user to use it. The disadventage of this method is that Beta expires after 90 days.
I am in process of developing app for windows phone 8. I need the adhoc distribution of my app to all devices within the organization. I don't want to publish it on the market instead i want the installation of app on the devices within the organization.
Do i need to buy another account for adhoc distribution or i can use the same $99 account for adhoc distribution of app.
Thanks in advance.
Well there are multiple ways to distribute apps,
Directly via Visual Studio or XAPDeploy (however the device must be developer unlocked, and connected via usb)
Via the normal Store/Marketplace
Via Store/Marketplace, with "Hide from users browsing or searching the Store" so that only users with the direct link to the store can find the app
Via Beta app distribution
edit: beta apps now do not have a 3 month limit anymore. Only restriction is, that you can "only" have 10000 users and each users email must be manually added for them to be able to download the beta
Company app distribution, which is likely what you are looking for. (However this seems to be relatively difficult) More information here: http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj206943(v=vs.105).aspx
Edit: I missed this one: Using "Windows Intune Direct Management for Windows Phone 8 Mobile Devices"
There are no other ways I know of.
I've seen the posts about requiring a signing code in order to access location functionality in BlackBerry (http://stackoverflow.com/questions/2876050/blackberry-location-api-not-working-correctly) but is this required even for a website? I too am getting 0 for both latitude and longitude... but signing codes appear to be for native apps, not websites. I would really appreciate any tips. Thanks!
The location API does not need code signing in order to access, but location data is considered priviledged and the application will need user permission to access it. There is also a system to allow the user to authorize websites to access location data but I`m not very familiar with it.
I talked to my boss who actually uses JS access to the blackberry location. He just followed the documentation here. Though he did say that before I upgraded him to a 9000 running OS 5.0 it was a bit hit and miss. The only other advice he had was it is slow and you have to wait for it.
Not sure if the title is quite right for the question but I can't think of any other way to put it..
Suppose you wanted to create multiple different web apps, but you wanted a user who was logged into one app to be able to go straight to your other app without re-logging in (assuming they have perms to look at the other app as well). If I'm not mistaken, if you're logged into gmail you can go straight to your iGoogle, googleReader, etc without re-logging in (if you set it up right).
How would you approach this? What would you use? Assume the apps already exist and you don't want to change the initial login page for the users.
What you're looking for is called Single Sign On. If you follow the link you'll find several implementations.
Open ID as others have mentioned is not such a scheme as it requires a seperate login for each site. Open ID is merely a shared authentication system.
You would issue a cookie against foo.com, which would then be visible on app1.foo.com, app2.foo.com.
Each application can then use the cookie to access a centralised authentication system.
Try CAS it should provide the features you are looking for.
What you want is a single sign-on (SSO).
There are two approaches to solving this problem:
Roll your own implementation. In its most trivial form it can be implemented by the first site setting a cookie that holds the ticket for the logged on user and the second site verifying that ticket and accepting the logged on user. There are quite a lot of potential pitfalls here:
you have to protect yourself against information disclosure - make sure that the ticket does not contain the actual user credentials
you have to protect yourself against spoofing - a man in the middle stealing a valid ticket and impersonating one of your users
and others
Adopt a third party SSO mechanism. Google, Microsoft, Facebook and other big companies allow integrating with their identity providers, so that your users could log on to their website and they handle verification, ticket issuing and so on. There's also OpenID, which is an open protocol you can use to enable SSO on your site through virtually any identity provider that supports OpenID. The potential drawback here is that somebody else controls your access to your user identity and can limit the features you can offer and data you can mine for your users.
As mentioned you can use something like OpenId or similar to make the process simple. Otherwise if you roll your own you could use a cookie to store the login, then basically ALL applications must have an entry point that mimics the base url.
Google for example uses mail.google.com to as a pipline into Gmail which allows it to read a cookie stored with the google.com domain.