You can modify code a little: remove register button. Then you can allow_frontend_register and only SOAP/REST calls can create users.
On Fri, Aug 31, 2012 at 2:24 PM, Edouard DUCRAY <[email protected]>wrote: > Hi,**** > > ** ** > > I just made a small portlet so that my portal (liferay) users can go > directly in our OM2.**** > > ** ** > > My first idea was ** ** > > try to login with current portal user credentials **** > > if I get a -10 return from (user does not exist) from loginUser call **** > > create this user in OM2 using addNewUser**** > > ** ** > > Here is my problem, if I have allow_frontend_register = 0 then I can’t do > this.**** > > Is there any way to allow new register from only several IP ?**** > > ** ** > > My last option is to use a SOAP only user , log this user and then using > setUserObject give name and mail information of my portal user. But this > way I’ve got strange thing :**** > > I’ve got new user created but not activated for the first portal user then > next are considered as the first one even if there name is changed. Bug in > OM2 or misconfiguration ?**** > > ** ** > > Small explanation :**** > > Portal username A mail [email protected] firstname F Lastname L**** > > Log threw my script :**** > > People see F L is connected if I try to reach him by mail it is the > correct mail.**** > > Admin see that a new user is created with this user information and not > activated.**** > > ** ** > > Then another Portal user log in threw my script B [email protected] Firstname > BF Lastname BL**** > > People see that BF BL is connected but if you try to reach him or see his > profile you’ll see user A information.**** > > No new user is created for this user.**** > > ** ** > > If someone have some idea…**** > > ** ** > > If someone is interested in my script, I’ll give it to community but it is > quite hugly for now.**** > > ** ** > > Sincerely,**** > > ** ** > > Edouard **** > > ------------------------------ > > -- > Cette communication est faite dans le but d'une utilisation par son > destinataire et contient des informations qui peuvent être confidentielles > ou protégées par des lois en vigueur. Si vous n'êtes pas le destinataire > voulu, la présente communication vous notifie formellement qu'un usage, une > copie ou une distribution de ce message électronique, dans son intégralité > ou en partie, est strictement interdite. Nous vous remercions d'informer > l'expéditeur dudit message par retour de courrier électronique, et > d'effacer ce courrier électronique de votre système. Ce courrier > électronique ne constitue ni une offre de contrat, ni un avenant à un > contrat, ni une acceptation d'une offre contractuelle, sauf si l’expression > « Aux fins de la conclusion d’ un Contrat » est expressément et visiblement > mentionnée. Ce courrier électronique ne saurait en outre constituer un > consentement à une utilisation des informations relatives à l'expéditeur > pour des raisons de marketing direct ou de transfert de données à des tiers. > -- > This communication is for use by the intended recipient and contains > information that may be privileged, confidential or copyrighted under > applicable law. If you are not the intended recipient, you are hereby > formally notified that any use, copying or distribution of this e-mail in > whole or in part is strictly prohibited. Please return this e-mail > immediately to the sender and then delete this message from your system. > This e-mail does not constitute a contract offer, a contract amendment or > an acceptance of a contract offer unless it is explicitly and conspicuously > designated as "Contract Intended". This e-mail does not constitute a > consent to the use of sender's contact information for direct marketing > purposes or for transfers of data to third parties. > -- > Leygatech, SAS au capital de 2.300.000 € , ZI Chambaud - 43620 St Romain > Lachalm - FRANCE - RCS Le Puy B 441 815 198 > -- WBR Maxim aka solomax
