On 24-01-2006 07:19, C Y wrote:
Can it be assume that without the ser_cred, there
is
no reliable way of populating the credentials table?
I found that www_authenticate doesn't work in the
presence snapshot. It seems that it cannot find the
relevant credentials for a particular 'user', even
though I have manually entered (what I believe to be)
the relevant entries (username, password, ha1, ha1b).
www_authenticate may be failing because I entered the
information incorrectly - but there's no way of
entering the information reliably without ser_cred, I
believe?
Yes, there is, you can enter the information "by hand",
corresponding hashes (ha1, ha1b) can be calculated
using gen_ha1.
Credentials table is in fact very similar to subscriber
table -- instead of username, domain, pair you have uid
column.
If www_authenticate could not find the credentials then
check whether you use correct realm (the first parameter
of www_authenticate).
Jan.
What does the UID column (replacing username and domain columns) look like? Is
it going to be username@domain??
Is there any particular reason that = searchable tables would be deprecated by
tables that require LIKE pattern matching for referencing?
If username/domain are removed in favour of UID, how does that affect other
tables which use username/domain (such as AVPs) ?
It all sounds so mysterious! :) I'm looking forward to a full rewrite of the
docs so that it will all make sense again.