Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auth Configuration is missing from WebSubHub PublisherClient configuration #1324

Closed
ayeshLK opened this issue May 5, 2021 · 0 comments · Fixed by ballerina-platform/module-ballerina-websubhub#131
Labels
module/websubhub Issues related to Ballerina websubhub module Team/PCM Protocol connector packages related issues Type/Bug

Comments

@ayeshLK
Copy link
Member

ayeshLK commented May 5, 2021

Description:

  • websubhub:Service could be secured with authentication. So, the developer should be able to provide authentication-config to the websubhub:PublisherClient configuration.

Samples

  • With authentication-config the websubhub:PublisherClient initialization should look like follows.
    websubhub:PublisherClient publsherClient = check new("https://localhost:9090/websubhub",
        auth = {
            username: "ballerina",
            issuer: "wso2",
            audience: ["ballerina", "ballerina.org", "ballerina.io"],
            keyId: "KEY_ID",
            jwtId: "JWT_ID",
            customClaims: { "scp": "hello" },
            expTime: 3600,
            signatureConfig: {
                config: {
                    keyFile: "../resources/private.key"
                }
            }
        },
        secureSocket = {
            cert: "../resources/public.crt"
        }
    );

Affected Versions:

  • Ballerina SL Alpha5

OS, DB, other environment details and versions:

  • Ubuntu 20.04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module/websubhub Issues related to Ballerina websubhub module Team/PCM Protocol connector packages related issues Type/Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants