Users vs. Accounts

[stevej]

The Mambo portal is overkill for my needs at the moment. And, I've run into too many issues getting it working reliably. So, I've decided to build my own simple portal using the SOAP interfaces, with the following functions:

1) User management - Login / Logout, Create New user (only if there is already a matching contact), update contact info
2) Case Management - CRU for the user's company's cases

Simple, right?

I'm running into one significant issue, though.

Users vs. Contacts. I can create a user to match a contact. And within my system, I can limit that User to seeing only cases relating to that user's company. However, a user is a user. It seems that the soap interface locks them in to seeing only cases for which the user is a contact. I still sometimes get the SQL in(,) error, but I can't reliably reproduce it,

I'm not sure I get the model, and the reason behind having contacts as effectively restricted users.

Thanks!

-steve j

[stevej]

What is the purpose of the portal_name field in the contacts table? For all of my contacts it's either explicitly NULL, or blank.

Thx!

-steve j

[stevej]

If I move the soap code into a Virtual server which is only accessible from the localhost, I can sort-of secure the Soap interface. Not elegant, but possibly good enough. I'm still stuck though on the probem with cases that I mentioned in a different post. When I go to the "Your Cases" link in mambo, I get a lot of debugging data thrown, with this at the beginning of it:



Connection Error

Response not of type text/xml



Anyone else see anything like this? Any thoughts?

thx!

-steve j