developer-portal | Developer portal for Kyber Network | Portal library

I have a powershell script that runs within my Azure Devops Release Pipepline for my API which uses the swagger doc from my API to automatically push changes into APIM.

The missing step is that once I have made the revisions, I need to update the developer portal with the latest schema and specifications. I can't have a developer going out and clicking the publish button every time we do a release.

According to this post I can get a token with a user id (not sure what userid it wants, I'm using a service principal) and do a post, but I was hoping there was an available utility in a module like I have been using for the rest of my script.

I am trying to direct the Root Context to the Developer Portal in WSO2 APIM tool, i followed this docs:

https://apim.docs.wso2.com/en/latest/develop/customizations/directing-the-root-context-to-the-developer-portal/

but i have no idea how i can open this file

i am trying to Directing the Root Context to the Developer Portal on the dockerized version of WSO2, but how i can keep the changes without edit files inside the container ?

I followed this docs:

https://apim.docs.wso2.com/en/latest/develop/customizations/directing-the-root-context-to-the-developer-portal/

Thanks

For reasons I can't explain, the Styling Guide page (Styles) in the new Azure API Management portal I am working on appears to be corrupted and I don't know how to fix it.

For example, the COLORS section is supposed to look like this:

But now looks like this:

I did a "Reset content" operation under the Operations menu item (several times) to no avail. I think this issue started after I did my first "Publish" of my changes, but I am not sure.

How do I fix the style sheet for this admin page?

I'm using Python to request things to the smashgg API (the queries are in GraphQL) and I got an error i never had before while running the code below :

I've successfully deployed the app from the tutorial here: https://github.com/awslabs/aws-api-gateway-developer-portal

Now, how can I either heavily customize the client or write a new one? Can I somehow do development locally and point the app to AWS resources. Are there any tutorials to do smth like that - write client and then integrate it with AWS IAM, Lambda and API Gateway. Or I have to do that within AWS environment? In this case do I use something like this: https://aws.amazon.com/getting-started/hands-on/build-modern-app-fargate-lambda-dynamodb-python/module-two/

I am using the Twitter API from Matlab, specifically by means of the twitter class from the Datafeed Toolbox.

I have essentially followed the example code from the official documentation. I created a Twitter app in my Twitter developer page, and obtained its API keys and access tokens. With those I can use the Twitter Standard search API from Matlab:

I am using SimpleSAMLphp (SSP) to handle authentication for my Yii website (via a remote IdP), and version 1.16.3 has been working fine. However, when I update my composer.json file and pull in version 1.17.2, the local PHP session on my website is no longer destroyed, leaving the user logged in. (The user is successfully logged out of the IdP, however.)

I did some Googling, and reviewed discussions that looked relevant:

• The change in how session IDs are generated, to comply with PHP config.
• Documentation about a mismatch between PHP session settings for the application and SimpleSAMLphp (as a possible source for session-related errors).
• The need to give PHP and SimpleSAMLphp different session cookie names: https://github.com/simplesamlphp/simplesamlphp/issues/365#issuecomment-212351265

I also reviewed some discussions in the SimplSAMLphp mailing list:

• https://groups.google.com/d/topic/simplesamlphp/k0AhOO8LLSk/discussion
• https://groups.google.com/d/topic/simplesamlphp/x8d53SkhEhE/discussion

In addition, I tracked the logout process using SSP 1.16.3 and 1.17.2 recording each Cookie header in requests, Set-Cookie header in responses, and session files in existence at multiple steps along the way, which showed some distinct differences... but I don't know what to conclude from this information.

When I begin the logout process on my website (which is built using Yii 1.x)...

1. I start by bringing up a clean docker container of my website, opening a fresh private Firefox window, and opening SAML Tracer. I verify that no session files currently exist on the server (i.e. in the new docker container).
2. I go through the login process.
   • 1.16.3 and 1.17.2 behave almost identically. At the end of the login process...
     • For both, my PHP session cookie's session file exists and is 7722 bytes.
     • 1.16.3: My SSP session cookie's session file exists and is 2294 bytes.
     • 1.17.2: My SSP session cookie's session file exists and is 2302 bytes.
3. I go to /auth/logout/ on my site, and the browser dutifully sends along my current PHP (PHPSESSID) and SSP (SimpleSAML) session cookies.
   • 1.16.3: no Set-Cookie headers are returned.
   • 1.17.2: a Set-Cookie header is returned for the SSP session cookie, but the value is the same as it was before.
4. I am redirected offsite (to the remote IdP) as part of the logout process.
5. I am returned to /simplesaml/module.php/saml/sp/saml2-logout.php/default-sp?SAMLRequest=… (and along go current PHP and SSP session cookies).
   • 1.16.3: a Set-Cookie header is returned for the SSP session cookie, but the value is the same as it was before.
   • 1.17.2: two different Set-Cookie headers are returned for the SSP session cookie, neither of which matches the previous value.
6. I am redirected offsite again, as a further step in the SAML logout process.
7. I am returned to / (the root of my site), with my (unchanged) PHP session cookie and (most recent) SSP session cookie.
   • 1.16.3:
     • a Set-Cookie header is returned for the PHP session cookie, giving it a new value.
     • the session file for the previous PHP session cookie has been deleted from the server.
     • the session file for the new PHP session cookie is empty.
     • the session file for the most recent SSP session cookie is 474 bytes.
     • I am no longer logged in on my website.
   • 1.17.2:
     • no Set-Cookie headers are returned, for either the PHP or the SSP session cookie.
     • the session file for the PHP session cookie is 7722 bytes.
     • the session file for the SSP session cookie is 338 bytes.
     • I am still logged in on my website (but not on the IdP).

I can (sort of) alleviate the problem by telling Yii during the logout process to return an empty value for the PHP session cookie (PHPSESSID) and set it to expire an hour ago, but since that leaves the session file itself still in place, that approach seems unsatisfactory.

Given that information, does anyone have any ideas or pointers on where I could look next to try to determine what might be causing this?

As things stand, I don't know if this is a result of me using Yii incorrectly, me using SSP incorrectly, or a bug in SSP 1.17.2.

I have not yet managed to distill this down to a minimal, reproducible example, and I apologize for that. The code is open source, though I doubt anyone wants to go digging through it:

• This commit of my code is how I tested SSP 1.16.3:
  https://github.com/silinternational/developer-portal/tree/2fa781f8bbdf9bb248038e18af64b024eb9a67e1
• This commit of my code is how I tested SSP 1.17.2:
  https://github.com/silinternational/developer-portal/tree/e581cbe0f309786cc99eab296896c8c7bdb29b99

What is the size limit for the 'name' field when creating an event with the Layout Automation Social Tables API endpoint?

https://developer-portal.socialtables.com/api-console#!/Layout_Automation/post_4_0_layout_automation