Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

phychem_ad
Community profile phychem_ad Level 2
Job title here
Location here
4 BADGES
Level 2

Level 2

Learn more
Joined the community 22-02-2017 12:55:24 AM
Offline
Top badges earned by phychem_ad
Customize the badges you want to showcase on your profile
Post-login page authentication in SPA editor
Avatar
Boost 1
Level 2
phychem_ad
Level 2

Likes

2 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Boost 1
Ignite 3
Give Back
Ignite 1
View profile
phychem_ad
- Adobe Experience Manager
Hi - i want to implement a member portal using AEM with SPA Editor. Members will need to be authenticated based on external identity provider like Okta. To elaborate the case a bit,1. user will login via a landing page. This page will be a pre-login page, where it'll just show some about the company details. This we know we can implement in AEM with an SPA editor mode as well.2. when user clicks login, he/she will be redirected to an external IdP (Okta), to authenticate, upon successful authenti...

Views

210

Likes

0

Replies

0
AEM SPA - determine .env file at build time
Avatar
Boost 1
Level 2
phychem_ad
Level 2

Likes

2 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Boost 1
Ignite 3
Give Back
Ignite 1
View profile
phychem_ad
- Adobe Experience Manager
The issue is related to the SPA React package at build time. We used the aem-project-archetype as the starting point. It included a ".env" file in the ui.frontend folder to specify the environment variables for the React app. The ".env" file is used to inject the environment variables to the React app when the project is built (mvn clean install -PautoInstallPackage --> npm run build). I have searched this forum and found that some people pull the runmode via some hidden html but this is not a d...

Views

254

Like

1

Replies

0
Re: Sitemap for SPA sites with AEM SPA implementation
Avatar
Boost 1
Level 2
phychem_ad
Level 2

Likes

2 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Boost 1
Ignite 3
Give Back
Ignite 1
View profile
phychem_ad
- Adobe Experience Manager
thanks @Vijayalakshmi_S @BrianKasingli in the case that my "When to use SSR" answer is no, may i know whether i still need to use the ACS commons sitemap generator to generate the sitemap (ie. is it even going to work on SPA sites) or assume(hope) that the main search engine will be able to evaluate the JS?

Views

428

Likes

0

Replies

0
Sitemap for SPA sites with AEM SPA implementation
Avatar
Boost 1
Level 2
phychem_ad
Level 2

Likes

2 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Boost 1
Ignite 3
Give Back
Ignite 1
View profile
phychem_ad
- Adobe Experience Manager
Hi we are implementing an SPA site with AEM 6.5+SPA editor, is there a way to generate a sitemap to optimize for SEO? or is SSR a must? and if SSR is a must, then using Adobe I/O also the recommended approach? with my previous implementation with AEM 6.3, we used the ACS commons sitemap generator https://adobe-consulting-services.github.io/acs-aem-commons/features/sitemap/index.html for non SPA app. Would this still work for SPA?

Views

496

Like

1

Replies

3
Likes given to
Likes from