I am having issues that when a user is not an Admin, that can't access a published application.
The spinner just keeps spinning indefinitely when try go to published app url.
Under Application access in the Edit deployment screen I do have 'Do not restrict access to this application' selected.
Related
I've built an app in App Maker and deployed it, but the user I thought I had given permission to is getting this notification "Sorry, you don't have access to this application."
In the app, I added a role to the data source and added the user to the role from the deployment. I also added the role to each page's security. I verified that App Maker is turned on for all of our users. I've ensured that the user has access to the Google Sheet data tables (both what I imported into the App for preview and the data I exported from the deployment). I've even added the user as a Cloud Sql Viewer in our Cloud SQL instance (don't know if that was necessary). This is my first app and I feel like I'm flying blind. I'm obviously missing something but can't figure out what. Any help is much appreciated!
Make sure all the required models can be accessed by the role you assigned to the user.
If the user has another Google account in the same Chrome session, the browser may be switching them to this external user when opening the app. Sign-out from that account or try incognito.
Make sure the deployment has no restriction as shown here; or if it does, allow the username.
I am using default actions in asp.net core web application for external logins. Currently I stuck with one thing. When you request to login via facebook, a facebook page loads and modal window shows up with permission approval of cancellation. Well, approval works fine, but what if I press cancel instead of continue? How to handle this request??
We have a web application that copies files to a remote server within our domain (OurDomain). The following issue occurs with users that log on to their laptop with another domain, and then log on to the web application with OurDomain. Users that log on to both the laptop and web application with OurDomain\User don't have this problem.
We have two webforms:
The 1st webform retrieves the user's ID using System.Security.Principal.WindowsIdentity.GetCurrent() and then sends an email with this userid. This code retrieves the user's ID only if we have Windows Authentication set to Enabled and ASP.Net Impersonation also set to Enabled. If ASP.Net Impersonation is set to Disabled, the user will be Network Service. So I set both to Enabled and everything here works great.
The 2nd webform copies some files to the remote server, also under the domain OurDomain. With Windows Authentication set to Enabled and ASP.Net Impersonation set to Disabled, then Network Service is used to copy the files to the remote server and are copied correctly. On the other hand, If ASP.Net Impersonation is set to Enabled, it seems to bypass Network Service and even OurDomain\User and tries to copy with, apparently, the credentials used to log on to the laptop (Another domain). The files don't copy and I get error Access to the path is denied
The only fix I've found is to add OurDomain\User to the folder, and it's really not a big deal, but I wanted to see why this was happening.
Thanks.
I believe OurDomain\User is the user who is logged into the system from web browser. It is not a good security practice to give server folder access to that group of users. If you give access to those users they can even browse the remote folder without your web application.
NetworkService is a user who has role on in the system where it is created.
Better create a user as asp.net appPool user in OruDomain\webappuser ie the user who runs the w3wp worker process. Let the password with be the admin.Give OurDomain\webappuser the permission on the remote folder. Run the web form without impersonation.
Now the files which are received via file upload dialog in webform2 can be copied to the folder safely as the asp.net application run in the context of OurDomain\webappuser
I've built an application (asp.net 2010) to allow our employees to update some of their information in Active Directory. Data like website, degree, campus, building, phone extension, etc.
Everything works fine until a user who is a domain admin attempts to use the app. Since the "service account" my .Net application is using is not a domain admin, the update fails for them.
Is there a way I can make this happen without having to make my "service account" a domain admin?
You could give your service account permission to the Domain Adminis object in AD (Read Write).
We are facing an issue with a SharePoint webpart we have developed.
After every app pool process recycle, thw webpart is not accessible to any users unless a local user accesses the webpart page first.
We recycle our application pools daily and unless a local user hits the webparty page, it is unavailable for all other users.
The error is : "Pge not Found".
Pointers on what could be causing this would be very helpful.
Kind regards
We had an identical problem on a project here recently. The problem then was that the anonymous user (guest user) didn't have the rights to load and compile the web part.
Our solution was to give the user that the anonymous visitors requests were run as rights to read the folder where the web part files were stored.
So I suggest you look at the same things. Which user is impersonated when an anonymous user visits your page and what rights does the user have. Most probably he doesn't have the rights needed to compile or setup the web part.
Have you tried to enable debugging and CallStack for your Web Application to get some more specific information about your error?