Hi IQ78,

If you're using Social Login Configurator, the Protected status is usually expected and doesn't necessarily indicate a problem.

A few things you can check:

• Make sure you published the consumer application that references the Forge component, not the protected module itself.

• Confirm that all modules from the Forge asset were installed and published successfully in Service Center.

• Try accessing the configurator URL directly after publishing:https:///SocialLoginConfigurator/

• Check Service Center for any publish errors or missing dependencies related to the component.

• Verify that the version of the component is compatible with your OutSystems platform version.

Could you share:

1. The Forge component link/version?

2. The exact message shown when you try to access the URL?

3. Whether the application appears as published successfully in Service Center?

That information should help narrow down whether this is a publication issue, a missing dependency, or a compatibility problem.

Thanks and Regards,
Akshay Deshpande

@IQ78 :   Inorder to run this follow the steps : Service Studio -> Search for 'Social Login Configurator' -> Open the Application and Click on 'Open In Browser' 

Hello @IQ78
 
Siya already showed you how you can open the Social Login Configurator in the Browser.

But I think it's worth to mention a couple things.

This application is considered a System Application. Like OutSystems UI. That's the reason why it says this application does not consume Application Objects (AOs).

System components can't be changed. Sometimes it may be useful to extract something from them. For example, you may want to adapt an OutSystems UI widget and it requires changes to it's internal logic.

In those cases, you clone the module and you can then extract or adapt the content to your like.
The original module will not be changed ad will still be "non-publishable", but you can work with the clone.

Cheers!