I am new to ejabberd. I am working on an instant messaging that will run across the globe with different languages.
My question is,
1) do I need to setup different server for each of these countries in the word.
2) can I implement VOIP across ejabberd
3) can I authentic users using their phone numbers
1) If you are worried about the 'language' option in ejabberd.yml, you can define a virtual host for each language, for example:
hosts:
- "example.com"
- "example.ru"
- "example.pt"
host_config:
"example.com":
language: "en"
"example.ru":
language: "ru"
"example.pt":
language: "pt-br"
But notice that this 'language' option only is relevant when ejabberd is replying to a client that didn't specify its prefered language. Try yourself to set the option to a strange language, and then login to ejabberd with your prefered clients... ideally ejabberd should reply in your language, not in the server-configured one.
2) From what I know, that's a client topic, so the servers do not interfere.
3) Well, the account username can be a number, why not?
13:50:09.190 [info] (<0.544.0>) Accepted connection
::ffff:127.0.0.1:43469 -> ::ffff:127.0.0.1:5222 13:50:14.311 [info]
(tcp|<0.544.0>) Accepted c2s SCRAM-SHA-1 authentication for
111222333#localhost by mnesia backend from ::ffff:127.0.0.1
13:50:14.390 [info] (tcp|<0.544.0>) Opened c2s session for
111222333#localhost/tka1
Related
I need to access a postgres database from my java code which resides in openshift cluster. I need a way to do so. without initiating port forwarding manually through oc port forward command.
I have tried using openshift java client class openshift connection factory to get the connection by passing server url and username password through which I log in to the console but it dint help.
(This is mostly just a more detailed version of Will Gordon's comment, so credit to him.)
It sounds like you are trying to expose a service (specifically Postgres) outside of your cluster. This is very common.
However the best method to do so does depend a bit on your physical infrastructure because we are by definition trying to integrate with your networking. Look at the docs for Getting Traffic into your Cluster. Routes are probably not what you want, because Postgres is a TCP protocol. But one of the other options in that chapter (Load Balancer, External IP, or NodePort) is probably your best option depending on your networking infrastructure and needs.
I know it's possible to whitelist IP-addresses for a route, but can you whitelist services by their name?
Running OpenShift 3.9.
Looking for a native solution that does not require external solutions like Istio, Nginx, etc.
I hope i understood your question correctly that you want to whitelist clients by dns name.
as far as i understand the docs from Openshift 3.9 [1] and the docs from HAProxy [2], i cannot see any option in HAProxy itself to build acls with dns names of the clients.
The only option available is ip whitelisting.
[1] https://docs.openshift.com/container-platform/3.9/architecture/networking/routes.html#whitelist
[2] https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#7.3
My web application is installed on many customer servers and the app needs to send emails via SMTP. Email smtp server is configured by the customer via a text (Properties) file.
I am having trouble deciding which settings should be included in the file. For some servers it is enough to let customer specify the following:
mail.smtp.host =
mail.smtp.auth =
mail.smtp.user =
mail.smtp.pass =
mail.from =
But which settings will cover vast majority of servers, so I have no worries that some setting will be missing?
An obvious approach would be to look at other mailers like Thunderbird or Outlook and see what configuration options they provide.
You definitely need an option that controls the use of SSL, which has three values:
Make a plain text connection
Make a plain text connection and then switch to an SSL connection using the STARTTLS command
Make an SSL connection to start with
These correspond to various settings of the mail.smtp.ssl.enable and mail.smtp.starttls.enable properties.
If you haven't already, you should look at all the properties described in the javadocs for the com.sun.mail.smtp package.
mail.smtp.auth should always be set to true.
That should get you started.
You may also want to let them specify the port.
Usually the following are used:
25 for SMTP
465 for SSL
587 for TLS
In SQL 2005 Reporting services we were able to spoof a user when calling a report. This doesn't seem to work in 2008 and the technet articles that appear relevant seem to be implying that you need to create a seperate security extension( Technet Article )if you're wanting to expose reports to the internet. Is this what people are using in production? Or is this simpler than I'm makint it out to be?
Not sure what you mean by "spoof a user".
Every version of SSRS to date has used Windows Authentication as the default (and in fact the only "out of the box") authentication scheme. If you wanted to do Forms Authentication you have always had to write your own Custom Authentication Module.
I have done both in Production environments depending on the situation, and their sample is a very good place to start building your own custom auth module
Simple Solution
in the rsreportserver.config add in the the Windows Basic Authentication:
Install apache >= 2.2 in the same machine (use other port than 80 for ReportServer) or on a other machine
activate mod_prox_http
Create a Browser User for Reporting service (for example "reportusr" with password "this#yourMachinepassw0rd")
define in http.conf
ProxyPass http:///ReportServer
ProxyPassReverse http:///ReportServer
AuthBasicFake reportusr this#yourMachinepassw0rd
Order deny allow
Allow from all
Now you can access the reportserver and all Reports over the apache Webserver with no authentication, because always the AuthBasicFake user connects to the reportServer with BasicAuthentication
How do I configure SSRS/Windows Server 2003, so that I can setup email delivery via a remote SMTP server that requires username and password.
I can configure SSRS with an SMTP address and other parameters, but nowhere is it possible to configure it with smtp username and password.
I have hunted around, but can only find vague reference to setting up some sort of relay, to cover up the bizarre lack of smtp functionality that SSRS has out of the box.
Any ideas?
Here are the steps to set this up using only Microsoft SSRS/Windows Server 2003 components.
1) Install SMTP server in Add/Remove programs / App Server / IIS
In IIS Manager:
2) add the domain (as a remote type) you will be sending as such as yourwebsite.com
3) Under Default SMTP Virtual Server properties / delivery tab / advaced button, add your remote smtp server in the smart host field.
4) Under Default SMTP Virtual Server properties / delivery tab / Outbound security button, choose Basic Authentication, user name = SMTP user name, password = SMTP password
In the rsreportserver.config file (sql drive:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer):
5) Populate <SMTPServer>x.x.x.x</SMTPServer> with the IP of the machine where you just setup the SMTP server.
6) Populate <From>you#yourwebserver.com</From>
7) Change this one to false <SendEmailToUserAlias>False</SendEmailToUserAlias>
8) Lastly, make sure you setup the domain as a permitted host such as this:
<PermittedHosts> <HostName>yourwebsite.com</HostName></PermittedHosts>
As far as why SMTP basic authenication isn't supported directly in SSRS seems to be by design. The best explaination I could find was here on this MSDN forum:
As one poster here mentions, there is a Microsoft Connect ticket open for people who are requesting this functionality.
For sure you have already solved this issue, but let me put here an additional information so others that have this same problem, like me, can solve it by following this how to that Tom Willwerth post.
To solve this issue of SMTP relay just follow the steps above, but be sure to do an additional step, that can be called:
4-a) On Access tab, choose Relay and select "All except the below" on Select which computer may relay through this virtual server:
This will allow all connections to send through this smtp, but be aware that the smtp server will relay anyone who connects to it. If you want to restrict this relay, than you choose "Only the list below" and add the machine you want to relay on.
For more detailed information on this, you can see the source where i found this information on:
http://businessintelligencechronicles.blogspot.com/2010/08/configure-reporting-services-to-use.html
And another thing, the step 8) isn't necessary .
Hope it can be helpful to others and thank you for the information, it helps and now i think one can solve this issue just by following this steps on this link.
Regards
Ps: sorry for the mistakes
This might help you a little: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\rsreportserver.config contains all of the configurations settings in the . I don't see exactly what you want so you'll probably have to perform some relay tricks.