How to setup Bugzilla without SMTP server (no need to use e-mails) ?
I installed Bugzilla from the windows-installer. We just use it locally and don't need emails, nor we have any SMTP server.
This link says that I don't have to have SMTP, but I don't know how to get to the "Administrator page"
You need to set the 'mail_delivery_method' parameter to None to disable sending email. Login as a Bugzilla administrator to get to the Administration page, then select Parameters then Email.
One needs to set the 'mail_delivery_method' parameter to 'Test'. Check for the new account creation mails in C:\bugzilla\data folder mailer.testfile file and you will get the token link there to actually create the new user. This way you can really bypass setting up a SMTP server totally but to use Bugzilla within a group of ppl. Very useful for small group developments and bug tracking.
Related
"Issue description copied..."
I'm building a partner connector, which relies on a user name and password to connect to database (very similar to the existing Postgres / MySQL connectors provided by Google). In order to verify the credentials, I also need the database host information to be present in addition to username and password and this is the base of my problem.
The Google build connectors conveniently are allowed to collect user credentials and the database related information at the same time. Unfortunately, that doesn't seem to be the case for partner connectors as stated in the requirements
Point 5 "Use appropriate authentication method in getAuthType(). Do not request credentials via getConfig()."
The authentication itself happens before any other configuration details are known (there is just a dialog for username and password) and there doesn't seem to be a way to request additional information on the authentication screen itself. Once the credentials have been entered, the verification also happens immediately, before the configuration is being shown in the next step.
Once credentials are validated successfully, Datastudio then assumes the schema and data can be requested.This excludes the option of a dummy confirmation, because there doesn't seem to be a way to tell credentials are invalid and need to be changed after checking the other configuration details on the next screen.
That makes me unsure, how to determine valid credentials in my use case as I need to know the variable endpoint to authenticate against. I definitely want to avoid storing any user credentials myself in an external database, because this opens up another can of worms.
Has anyone successfully solved a similar issue before and can provide guidance here?
This is a known limitation of the authentication methods for Community Connectors.
A workaround would be to use authtype NONE and then request the credentials and database information in the config. This is, however, not a recommended approach.
I can access my reports through
http://mymachine:808/Reports
or
http://localhost:808/Reports
but not
http://myhost.mydomain.com:808/Reports
even when I have myhost.mydomain.com map to 127.0.0.1 in the host file. It was keep asking user name and password, but the same user name and password works fine in other ways to access.
How to fix this?
Update
It prompts to type in user name and password, but just to pop up again. So there is no way to get into the page with the broken URL.
This is consistent in at least 2 browsers: Firefox 47.0, and Edge 25.10586.0.0
Also, I didn't have Report Manager installed, here is my menu of Reporting services configuration manager:
From the hint in comments the issues is in the Reporting Services.
I was using the default settings, but MSDN said you can have different authentication types. I checked my reportserver.config file and I was using NTLM. Change it to use basic authentication solves the problem.
My guess of the reason, is that the browser will send a "Host" property for every request, and as this is inconsistent with NTLM's "domain", so Reporting Services reject the authentication. However, when switch to basic authentication, it simply pass the credential to Windows, so now it accepts.
References:
Authentication Types in Reporting Services
How to: Configure Basic Authentication in Reporting Services
You could try adding a new URL for Report Manager. To do this
Open Reporting Services Configuration Manager
Select Report Manager URL
Click Advanced
Click Add to add details
Here's a screenshot to help.
Can SDL Tridion, by default, talk to the active directory based on the domain of the server where Tridion is installed?
o Ex: we install tridion in the server server1.abc.com where abc.com is my domain
If it cannot be done by default, can you please let me know how we can configure it?
Yes it can be done - this is the default behavior.
In the Add User dialog you should be able to type a domain name, and if the server (and the server's user account, MTSUser by default) is allowed to talk to that domain you'll get a list of the users and you can add them to the list of allowed Tridion users.
Nothing to configure unless you want LDAP integration.
I've set up LDAP authentication using pam_ldap on a server and it seemed to be working just fine to begin with, but now I have a problem. Whenever a user changes his password in Active directory, it syncs just fine with LDAP and therefor every system that uses LDAP authentication, except this server which still accepts the old password.
I've tried "getent passwd" and it does list every user in LDAP, and I also tried adding a new user in LDAP, which my server immediately recognized when I try "getent passwd" again.
So apparently my server is commmunicating with LDAP, just not when it comes to new passwords, those the server chooses to cache somewhere.
Google hasn't been helpful at all and some people seem to have had similar problems but their questions always go unanswered.
Hope someone can help.
You may have nscd installed. Check /etc/nscd.conf and lower the TTL.
I'd like to have emails to a given domain, say http://mydomain.com/, processed by an AppEngine app, let's call it http://emailprocessor.appspot.com/ .
That is, an email to "hello#mydomain.com" should be received and processed by emailprocessor.appspot.com as if it was an email to "hello#emailprocessor.appspot.com" .
I imagine I could do this via MX records for my mydomain.com domain, but I can't find instructions anywhere.
Is this possible, and if so does one set it up?
Also there is no direct support for this according to documentation
BUT
if your http://mydomain.com/ hosted on google apps and you create user hello#mydomain.com as gmail account and in it configure email forwarding rule to the "hello#emailprocessor.appspotmail.com" it should work as it works for any general gmail account email forwarding. It preserves original headers like sender etc.
I almost sure that most of other mail services or servers can support this feature. check documentation of your mail service.
PAY ATTENTION! it must be emailprocessor.appspotmail.com note the appspotmail.com not appspot.com
I did not try it myself yet so I will be happy if you confirm that this works. Again it should.
What I have done is to point the MX record to a server that allows you to do email domain forwarding. Then you can forward all emails to emailprocessor.appspotmail.com.
The advantage of this is that you catch all usernames: hello#mydomain.com, goodbye#mydomain.com, etc...
If your host has cPanel see this: http://www.siteground.com/tutorials/email/email_domain_forwarding.htm
No, there's no documented support for receiving mail on a custom domain.
You would need to host mail elsewhere and configure a forwarder to emailprocessor.appspotmail.com.