13

It's my understanding that custom authentication schemes invalidate the confidentiality clause of the Salesforce.com Master Subscription Agreement and thus would violate your TOS. If you are building an app for the AppExchange, you would not pass security review.


10

It is the Owner of the Account the Portal User Contact record that needs to have the role. The HVP User will inherit the role hierarchy from the Accounts Owners profile. First, create the user that will own the account, and make sure they have a Role. Then create the Account, owned by this user, then, the contact related to the account. Last, create the ...


8

This discussion forum thread suggests that you can do this with https://<instance>.salesforce.com/secur/frontdoor.jsp?sid=<sessionId>&orgId=<orgId>&portalId=<portalId> Change <instance> to the relevant instance, e.g. na1, and substitute in the relevant IDs.


7

This is possible with force.com sites . With force.com sites you can build visualforce pages that can be accessed by an anonymous user . The other option is to configure a simple web to Lead form your SFDC instance ,where from your website you can capture the leads and have an internal process for creating community users .


6

As mentioned, these have all been subsumed into Community, the portal to rule them all. For the curious, here's the lineage. Self-Service This was the very first portal. It's main draw is it's FREE. User management is funky (not stored in the User table), and customization is extremely limited. Partner / Customer Portal These are the second portal ...


6

I suggest code like that below, where once the password verified login has succeeded you go on to check further factors (that you have added as fields to your login page): global with sharing class CustomLoginController { global String username{get;set;} global String password{get;set;} global String other1{get;set;} global String other2{...


6

I've done pretty much exactly what you describe before. Rather than using the inactive flag, I used a custom Boolean to represent that the user had not self-validated, and used this to deny access upon login. It seems the right approach to me and isn't much work. AFAIK there is no official support for user email validation for self-registered users but I ...


6

The image file logo180.png is obviously deleted or moved (or was never there). I found that this error also shows in our org as well if you you open developer tools and refresh the page. I did a little digging and it appears the file is related to some marketing survey Salesforce created. Here's the line in my org: <script>var SFDCMktUrl='https://...


6

There is no solution to this since you have consumed all the license that were allocated for your org . Deactivate the existing users if you are testing your code . You can also purchase additional license to avoid this .


6

Just to add to @John Thompson's answer, you can add the button that disables the customer user: This will remove the connection between the user and the contact, and mark the user as deleted. If you don't have this button - you can add it to your layout from the page layout editor: After removing the connection between the contact and the user you can ...


5

The technique above worked great for me. I used it in a Schedulable interface as triggers can't employ the getContent method. We just run this nightly. Below is the code I used to implement in our Org: global class LicenseAvail implements Schedulable { public String result; public String orgName; public String orgCountry; global void execute(...


5

Customer Community users don't have permission to view Opportunities because their license doesn't allow it. The only way around this is to create a mirror object with Opportunities using a trigger to keep the object in sync. You can then display your custom mirror object records to your Customer Community Users. Otherwise, you'll need to purchase Partner ...


5

Since you're using a custom login screen, I'd also customize your forgot password screen to propagate that state back to the login screen. Pass it and return it as a startURL


5

You can query the Status of the Network object. If there's a community, there will be an Id. The Status will tell you whether it's Live, Down for Maint, or Under Construction. I believe you'll need to have “Modify All Data,” “View All Data,” or “Create and Set Up Communities,” to access the object. See the Object Reference for more.


4

Using Salesforce Communities: Edit the Community's Login Page, and ensure that your SAML IdP is the only selected login option: Now users will be automatically directed to the IdP for login, instead of seeing the Salesforce Community login page. For Internal Users You need to create a My Domain (see documentation). My Domain gives your org a custom login ...


4

Yes it will fire! After all its a trigger and it will fire based on the DML events that are added in the Trigger. Self Registration is a KIND of DML (INSERT) and hence your Before Insert trigger will fire.


4

It is possible. Your customer portal works as any other site for Google analytics. You only have to add the javascript snippet that Google Analytics gives you when you are configuring your account. It is always a good idea to put this code on a component to include into all your site pages. Also you could use templates to add it to all pages at once. ...


4

I'd discourage Portal creation other than in Dev orgs - any new Portal developmnent should stand on the shoulders of Communities instead. If you replace Portal with Community, a lot of the existing documentation holds true. Also watch out, I don't think you will get a Portal or a Community to live on your Salesforce domain. Which one of these portals ...


4

I was able to figure it out FINALLY! I was inspecting the actual XHR request in Chrome dev tools. I noticed under ctx under the payload there was a ver property. I realized this corresponded to the API version of the controller and was 32 in the page that worked and 28 on the one that didn't. So the page that worked extended the controller of the page ...


4

it works when you use the global profile variable: rendered="{!$Profile.Name == 'Your Profile Name'}"


4

This is a known issue (4+ years old) in the platform - see Allow underscores "_" in email domain fields. Add your vote and comment but you will have use a workaround (e.g. alternate text field) for the foreseeable future.


4

You will create a Report on User Object where ContactId != '' .Please check the below screenshot If a Community User is created then a User record has a contactId populated to link the contact with that User .


4

First, you'll want to create your RunAs user who should be someone with the profile that has the permissions needed to create accounts and enable your contacts as portal users. Worst case, that can always be a System Administrator. I usually create a Test Class Utility in most orgs that creates an Admin User for me and a "Standard User" to use for testing. ...


4

You can easily catch the exception from debug logs Just go to generic exception page in the VF page code you will find line <apex:param value="{!$Site.ErrorMessage}"/> change that to <apex:param value="{!$Site.ErrorDescription}"/> and after that when you will run your page you will get detail exception also in your debug log you will complete ...


4

This Knowledge Article User license conversion when migrating from portal to communities covers the transitions that are simple: An administrator can change the license type and profile on the user record. and the transitions that when attempted result in the error message: cannot upgrade from or downgrade to LPU and so require this disruptive ...


4

I'm fairly certain that NULL is case sensitive. Try this: <aura:if isTrue="{!v.user != null}"> And it looks like the user is never null. If the user has not logged in, then they are a Customer Portal Site Guest User. If they have, they will get some other name. You should probably make your test something like: <aura:if isTrue="{!and(v.user != ...


4

I would probably try to use the <aura:If> statement to conditionally SHOW fields rather than hide them. This way they won't appear and then disappear. Ie, show the desired fields to users who are not the guest user: <aura:if isTrue="{!and(v.user != null, v.user.Name != 'SFDC Comm Guest User')}"> <!-- fields that you want to only show for ...


4

Please use below code to redirect to community login page : window.location.replace("<community-domain>/secur/logout.jsp?retUrl=<redirect-URL>"); Eg: window.location.replace("/testPortal/secur/logout.jsp?retUrl=%2Flogin"); window.location.replace("https://mycommunity-domain.com/secur/logout.jsp?retUrl=https%3A%2F%2Fmycommunity-domain.com%...


3

The first thing to understand is that customer portal users don't have access to the sharing model and role hierarchy so your bottom two suggestions won't work. Customer portal users are only allowed access to objects that they own or objects that are associated via lookup to the portal user's account or contact record. This is done via Sharing Sets. ...


3

Second OAuth 2.0 call, obtain access and refresh tokens, remains as it was used for standard salesforce. Note : It is important to be careful when doing log off from Portal. User should be moved from both domains - standard salesforce domain and portal specific domain. If this was not set, user will be logged off only from standard domain. This results with ...


Only top voted, non community-wiki answers of a minimum length are eligible