Forum Discussion
5 Replies
- PaoloT12 years agoLithium Alumni (Retired)
Hi mayank
it is generally not advisable to embed credentials in a link - it can pose significant security risks. What is the use case that you are trying to solve?
Thanks,
I'm trying to accomplish this - If a user/customer registers on my site for a product, he recieves an e-email containing the link to the community site which when clicked opens up the product video on community site. What we want here is to have this user logged in to community with some generic user id?
- nathan12 years agoExecutive
Why does the user need to be logged in when they follow the link? Why do you want them to use a generic user?
It's something that when a user registers to my company's site, he gets an email in which a link is embeded and it directs to the company's community site when clicked. We want the user to be logged in to community once he follwed this link and that's because of the following two reasons.
1. It should be a good user experience that he is not asked to login (as he is already registered with the company's site for any product) to the community to view the content
2. On ourcommunity, we have restricted our content (through freemarker) to be not viewed by the non-regitered user, so this user if not logged in (say we would create a generic user for such logins on our community), won't be able to the desired content on community
Any help will be much appreciated here, thanks!!
- PaoloT12 years agoLithium Alumni (Retired)
Hi mayank
the scenario you are describing seem to imply a Single Sign On flow (i.e. there are two separate systems - the company website which has a registration system and the Lithium community which I am assuming is set to use the standard Lithium authentication, and you want the log in state to propagate from one to the other). In Lithium we support single sign on in a variety of flavours so this may be of interest. I am not fully convinced that the solution you are looking at would be ideal from multiple perspectives.
My suggestion is to either look up at the standard Lithium SSO implementation which requires some development at your end and configuration at Lithium's end (there is plenty of documentation on the Lithosphere or you can ask support), or to get in touch with Professional Services to explore other possibilities.
Thanks,
Related Content
- 4 months ago
- 6 months ago
- 4 years ago
- 3 months ago