similar to: login case sensitivity

On 09/05/2017 06:01 PM, Yves Bellefeuille wrote: > FHDATA wrote: > >> some users' login fails since they type upper >> case for their user ids ,etc ... > Wouldn't it be better to explain to the users that the userid is case > sensitive? You probably don't want a system where Fhdata, FHData and > FHDATA are all possible and are different users. >

On 5 September 2017 at 17:27, FHDATA <fhdata at unm.edu> wrote: > > > hello, > > some users' login fails since they type upper > case for their user ids ,etc ... > > how can case sensitivity be disabled so they can login > with mix of upper and lower case? > > this is what i tried: > > in /etc/sssd/sssd.conf i tested this below > >

Dear all, I'm running CentOS 7.3 with SSSD. I'm using sssd-ad to talk to an AD backend. Group names in the AD contain capitals. When sssd-ad is working normally, group names returned are all lowercase. However, when the AD backend goes offline, group names returned from the SSSD cache contain capitals. The change in case breaks stuff (sshd's AllowGroups, for one). Has anybody

On Sat, September 16, 2017 1:45 pm, Yves Bellefeuille wrote: > H <agents at meddatainc.com> wrote: > >> I have been using the KeePassX password manager on CentOS 6 and 7 for >> some time and it works pretty well. On my Windows machine I use >> KeePass which offers a number of features missing from KeePassX, I >> also sync the database between several machines,

FHDATA wrote: > some users' login fails since they type upper > case for their user ids ,etc ... Wouldn't it be better to explain to the users that the userid is case sensitive? You probably don't want a system where Fhdata, FHData and FHDATA are all possible and are different users. -- Yves Bellefeuille <yan at storm.ca>

Hi John, Thanks for pointing me to case_sensitive, that indeed is the cause: the default for "case_sensitive" is "True", but for the AD provider "True" is invalid(??), so it defaults to "False"(???)! Good news is that with both "case_sensitive = False" and "case_sensitive = Preserving" the results from AD and cache are identical

Why can I do this.... validates_uniqueness_of "username", :case_sensitive=>false .... but not this.... User.where "Xx", :case_sensitive=>false ? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

Is IMAP supposed to be case sensitive or case in-sensitive? It seemed it would be case sensitive because I've had different cases of folders. But today I found I had two folders "Spam" and "spam", with directories ".INBOX.Spam" and ".INBOX.spam" on the server. Messages existed in each directory on the server and they were different. The messages

I have also posted this on IRC. I have a linux host running stock RHEL 5.4 Samba 3.0.33-3.15. The host acts both as a Samba server and does a CIFS mount of that same share. The reason for doing this is so that programs running on the Linux host have the same case insensitive view as the Windows clients. I have nocase set in the relevant line in /etc/fstab I have case sensitive = No set in the

On Fri, 20 Jan 2017, Robbert Eggermont wrote: > Dear all, > > I'm running CentOS 7.3 with SSSD. I'm using sssd-ad to talk to an AD backend. > Group names in the AD contain capitals. > > When sssd-ad is working normally, group names returned are all lowercase. > However, when the AD backend goes offline, group names returned from the SSSD > cache contain

On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: > This was always > problematic because DNS hostnames and email addresses in the RFC > standards were case insensitive Not quite.? SMTP is required to treat the "local-part" of the RCPT argument as case-sensitive, and to preserve case when relaying mail.? The destination is allowed to treat addresses according to local

Hi, I have recently updated from Dovecot 2.2 to 2.3. Since I have noticed that vacation responses from sieve are not working the same anymore. For example, my sieve script looks like this: vacation :days 1 :addresses ["Kippels at hhu.de","julian.kippels at hhu.de"] it used to be that I got a vacation response if I sent a mail to kippels at hhu.de and Kippels at hhu.de. Now

Am 07.09.2017 um 20:07 schrieb hw: > Gordon Messmer wrote: >> On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: >>> This was always >>> problematic because DNS hostnames and email addresses in the RFC >>> standards were case insensitive >> >> >> Not quite.? SMTP is required to treat the "local-part" of the RCPT >> argument as

Hi- I've got a weird case sensitivity problem. I've looked through past messages but haven't been able to find a solution. This is an environment using samba to mount shares from a Solaris machine onto a Red Hat machine (originally done because of 16-bit UID limitations in Red Hat 6.x). Now I've upgraded to Red Hat 7.2 (samba 2.2.1a) and the share from the Solaris machine

Is there anything about this analyzer that says "case-sensitive" to you? module Ferret::Analysis class StemmingAnalyzer def token_stream(field, text) StemFilter.new(StandardTokenizer.new(text)) end end end Just wondering how I can force my index to be case-insensitive. Thanks, -Adam -- Posted via http://www.ruby-forum.com/.

Hi, Yesterday I found big problems concerning my roaming profiles. They seem to work on some computers where they are always used, on some other the did not load properly (i.e. a default profile was loaded instead). After some debugging with userenv.log I found the very strange problem: case sensitivity for ntuser.dat!: [...] IsCentralProfileReachable: Testing <F:\testuser\ntuser.dat>

Hi All, I am trying to match two character arrays (email lists) using either pmatch(), match() or charmatch() functions. However the function is "missing" some matches due to differences in the cases of some letters between the two arrays. Is there any way to disable case sensitivity or is there an entirely better way to match two character arrays that have identical entries but written

I want to add case_sensitive option to inclusion validation. This will allow to do: validates :numbers, :inclusion => { :in => %(One Two), :case_sensitive => false } Does it make a sense? Thanks. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit

On 9/6/2017 3:45 AM, ken wrote: > I think it would also be a disservice to users, for case-insensitive > userids is not what they'll find on web sites and web services > throughout the rest of the world, even on their own phones. I agree with you on other points, but beware of this one. I've discovered that game logins, notably Blizzard, are case-insensitive. It's quite

https://bugzilla.mindrot.org/show_bug.cgi?id=2685 Bug ID: 2685 Summary: Case sensitive hostname matching Product: Portable OpenSSH Version: 7.4p1 Hardware: Other OS: All Status: NEW Severity: normal Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org