ColdFusion Font Management with a non-administrative account - coldfusion

In the interest of making my ColdFusion 9 server more secure, I recently changed the "Log On" account for the CF Application Service to a non-administrative account. Everything is working fine with one exception: Fonts are no longer available through the "Font Management" tools in CF Administrator. This came up because I use CFDocument to render .PDF files and with the non-admin account they went to using only Times New Roman as the font. I've made sure that the service account I created had Full Control rights to the Windows Font directory, and I even copied all the fonts to a non-Windows directory and tried to add them from there. In both cases, the fonts cannot be added using the Font Management tool and do not render in CFDocument. I get no error when attempting to add the fonts - just a blank screen. Only thing I can find in the logs is a reference to org/jpedal/exception/PDFFontException.
Anyone out there had experience using a non-admin account to run CF Application Server and what I need to do to get the fonts to work properly?

Can you try giving permission to \ColdFusion9\wwwroot\CFIDE\administrator\settings or \ColdFusion9\wwwroot\CFIDE\administrator\settings\fonts.cfm?

Related

Sitecore content editor redirects to Page not foud

Due to some publishing issues i corrupted my local enviroment. Luckily i had backup which i restored and my local site was functioning well but, when i login to sitecore and choose any option from main page like Content Editor or Desktop it redirects to page not found.
I've tried to disable exceptions which redirect to page but they were of no use. And no logs are being created. Should i replace the entire wwwroot folder but, my wwwroot backup is 2 months old.
Or should i start from scratch and create a new sitecore site for same solution. I've compared my web.config,connection strings files they don't seem o have any problem.
Suggest what to do.
You are able to login but seems due to some permission issue you are not able to Content Editor/Desktop. Check permission on folders like identityserver(used for login)/your website(content editor and other CMS work), to start with you can try to give permission to your IIS User/Everyone (as shown in image), once it starts working you can be selective and change permission as per your need
enter image description here

Google Cloud doesn't allow me to create my first project with admin role

I'm trying to create my first project in google cloud with organization's administrator account. I have access to the administrator's email and passwords and I am logging in with that account to do so. The problem is that when I click on create new project I receive the following error:
There was an error while loading /home/dashboard?project=proven-now-305315&authuser=1.
You are missing at least one of the following required permissions:
Project
resourcemanager.projects.get
Check that the project ID is valid and you have permissions to access it. Learn more
Send feedback
The detail is that in my resource administration panel I already gave the permission that they ask me to the resource as shown in the following image:
As I have read, the project IAM Admin role should grant the resourcemanager.projects.get role and as you can see in the image the resource rcv # .. which is the administrator has it activated, however I keep trying to create a new project and it doesn't allow me to do it. Any idea?
In case anybody else, like me, reaches this answer, I want to point out that the accepted answer is correct, but for me I had to also make sure that within the settings, I ensured that Project Creation Settings on the right pane and under the section of Cloud Resource Manager Api Settings was set to on. It was turned off by default. Many people on my team overlooked this as it is significantly smaller text.
This may be an option that was not present before or it was turned on by default in the past. For us, it was turned off.
Please refer to the included image for a visual representation of the
settings that need to be turned on.
The problem was for some reason the Google Cloud was disable for all users, I solved following this instructions. Solved with this!
To activate this service, please follow the steps:
Access the admin console and go to Apps -> Additional Google Services
Look for the service “Google Cloud Platform” and click on the box next to it
In to top right corner click in “ON”
Confirm you want to turn it on in the pop-up box.

I got an error while trying to publish my Android app that read: "You told us your app doesn't comply with the Location permissions policy"

[google-people] I have an Android app that I recently published to the play store. I got an error while trying to publish the app that read: "You told us your app doesn't comply with the Location permissions policy". I am not sure what this means, but here is some context about my situation.
My app, the one I tried to publish is a flavor of another app. So, I have a Main app and a copy of Main(the flavor app). The copy contains all the features and functionalities of the Main app, with modifications to the colors and assets of the app. For this copy(flavor app) I did not require background location so I removed it from it's manifest. I did not remove it from Main's manifest. Just the copy(flavor app). So, Main app's manifest has the the background location permission enabled, but the copy(flavor app) does not.
Is it because my flavor app does not have the background location permission enabled? According to the developers page:
"Manifest files that were part of the build but did not contribute elements or attributes are listed under Other Manifest Files on the right." So, although Main's manifest gets merged into the flavors, it does not contribute elements or attributes to the final apk buid of the flavor.
I would highly appreciate some clarification and understanding to this issue.
Please see attached image or go to: https://developer.android.com/studio/build/manifest-merge#implicit_system_permissions?
According to the Requesting access to background location, Google Play requires a strict(er) set of requirements to be able to use background permissions for apps installed via the Google Play store. It provides a set of guidelines which have to be fulfilled to allow an app to enter- or remain in the store with said permissions.
In short you have to follow the steps given below at Google support to verify your apps location permission requirement.
https://support.google.com/googleplay/android-developer/answer/9214102?hl=en#zippy=

Set access permission on an application as antivirus do

I am trying to set permission on an application as read/execute only, I can achieve this by using c++ windows SetSecurityDescriptorDacl() function.
But after that admin can change it by right clicking on a file
properties->security->advanced->Change Permission
But somehow antivirus prevents these charges on their application as shown in below image

Meteor Facebook Login "You are using a display type of 'popup' in a large browser window or tab" Error

I am using meteor accounts-ui/accounts-facebook to login and am getting the following error.
You are using a display type of 'popup' in a large browser window or tab. For a better user experience, show this dialog with our JavaScript SDK without specifying an explicit display type. The SDK will choose the best display type for each environment. Alternatively, set height and width on your window.open() call to properly size this dialog if you have special requirements precluding you from using the SDK. This message is only visible to developers of your
http://goo.gl/IBmdjI (screenshot)
I haven't been able to find any information on the fix anywhere. Is this something in meteor core that needs to be changed?
This isn't a issue really its just a warning. Meteor doesn't use the JS Facebook SDK and gives a specified height/width for the facebook OAuth dialog & your browser size may be too big for the small popup (not too sure- looks ok in your screenshot).
If you disable your app from Sandbox mode/another user uses your app they wouldn't see this warning anymore.
The alternative is to use a redirect to facebook or a mobile display. The best option is the popup (what you have now) because it's the fastest: A redirect means your Meteor app has to reconnect up.